Options to customize session watcher behavior

[renkun-ken]

There are plenty of issues requesting options to customize session watcher behavior. This issue is a collection of all existing issues regarding session watcher options.

• Plot created by plot functions:
  • Device: Disable show plot  #277
  • Viewer: Suggestion: allow plots from session watcher to share editing pane #331
• WebView in general:
  • Theming: Better support of dark theme in WebViews #178, WebView color scheme (black on black) can make text almost impossible to read #172
• browser webview created by shiny, R help, httpgd, etc.
  • Viewer: R graphics device with HTTP access. #329 (comment), How do you open webview in new window automatically? #243, utils::browseURL #166
  • Proxy: Modify function browser / argument url (options) to allow proxied requests #275
  • Search: Improve R documentation integration #204
  • Customizable port mapping: Using WebView in Docker when port is not exposed #192
• viewer and page_viewer webview created by htmlwidgets, profvis, etc.
  • Viewer: How do you open webview in new window automatically? #243
• Data webview created by View()
  • Viewer: How do you open webview in new window automatically? #243
  • Replace existing: Replace existing webview with same title instead of open a new one #214

I'm thinking of defining more options to allow users to customize the behavior of session watcher so that different features (e.g. plot) could be disabled, and the viewer of browser, viewer, page_viewer, and View() could be a VSCode ViewColumn (Active, Beside, etc.) or external (open a web browser on client side like R's native behavior).

[benz0li]

@renkun-ken May you/we have another go at issue #275?

The integration of httpgd works fine with VS Code but not with code-server. This is because the url points to 127.0.0.1 (localhost) instead of the URL at which code-server ist running.

I'm happy to provide you with a dev environment. You will receive an email with more details asap.

[renkun-ken]

@benz0li Thanks for providing a dev environment.

[benz0li]

@renkun-ken Just tell me, if you need additional Linux packages for development.

[benz0li]

I have set up a dev environment at https://vscode-r.jupyter.b-data.ch. Sign in is done with your GitHub account.
ℹ️ Whitelisted users: @renkun-ken @Ikuyadeu

The setup is based on https://gitlab.b-data.ch/docker/deployments/jupyter and currently running

• JupyterHub v1.4.1
• JupyterLab v3.0.16 including
  • code-server v3.10.2 (aka VS Code v1.56.1)
  • Extensions: R v1.6.8 and R LSP Client v0.1.14
  • ...

👉 Full specification of the JupyterLab image at https://gitlab.b-data.ch/jupyterlab/r/r-ver/-/blob/master/r-ver/latest.Dockerfile; plus libxt-dev installed in addition.

I’m happy to further customize the Docker image, i.e. adding any Linux package you need to get your work done.

---

Default code-server settings.json in the JupyterLab image:

{
    "editor.tabSize": 2,
    "telemetry.enableTelemetry": false,
    "gitlens.advanced.telemetry.enabled": false,
    "r.bracketedPaste": true,
    "r.plot.useHttpgd": true,
    "r.rterm.linux": "/usr/local/bin/radian",
    "r.rterm.option": [],
    "r.workspaceViewer.showObjectSize": true,
    "workbench.colorTheme": "Default Dark+"
}

ℹ️ Thus, using radian and R Session Watcher by default.

[benz0li]

FYI https://vscode-r.jupyter.b-data.ch has been updated:

• JupyterHub v1.4.2
• JupyterLab v3.1.14 including
  • code-server v3.12.0 (aka VS Code v1.60.0)
  • Extensions: R v2.3.0
  • ...

https://github.com/cdr/code-server/blob/main/docs/CONTRIBUTING.md#requirements are installed, too.
ℹ️ coder/code-server#3661 is still an open issue, though.

[benz0li]

ℹ️ It is now possible to develop VS Code Extensions with code-server (v4.0.0+), because it has been rebased on upstream's newly open-sourced server: coder/code-server#3661

[github-actions]

This issue is stale because it has been open for 365 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 14 days since being marked as stale.