New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Store RStudio user preferences in a user-accessible location #1607
Comments
|
A natural extension of this work would be to allow for a "global defaults" settings file to be read from a shared location, for use by administrators who wish to set defaults for their users according to constraints/patterns in their environment. |
|
I second to this possible feature. When I wrote rmarkdown documents, I found it has been very useful to change chunk evaluation location from |
|
Bump, as a user interested in this feature. ;) |
|
I too that this would be a great feature for RStudio. As an rstatsnewbie working on a couple of different machines (work & home), being able to sync packages and settings between them would be greatly appreciated!!! |
|
As the foundation of a third party tool for syncing different installations of Rstudio this would be a killer feature |
|
I guess anything/everything from 'Global Options' would be good |
|
It would be great if it was possible to streamline retrieving and modifying the configuration ala the state information given at: https://support.rstudio.com/hc/en-us/articles/200534577-Resetting-RStudio-Desktop-s-State As it stands now, this is largely done through posting pictures. Unfortunately, this creates headaches for newer users... |
|
It would also be convenient if local settings (e.g. in a directory containing an |
|
Not sure whether this is a common use case for others, but when my RStudio Server instances crash I often have to manually reset all options. Being able to import settings somehow would be great when creating new instances. |
|
See here for another example of how configuration is shared in the absence of something like this: |
|
RStudio Server Pro customer requested, ticket 37036 |
|
Another useful option to include in a config file is how to filter the files that are displayed in the Files pane, as noted by @kevinushey in #3383 (comment) |
|
This change won't add any new options; it will only change the way we store existing ones. |
|
Just to say, many thanks @jmcphers this will make lots of peoples lives lots easier when this is rolled-out. I'm planning on using it to create a custom docker image optimised for academic geographic research, with Rmd chunks evaluated in-line. One question: will we be able to set shortcuts through the plain text file? Many thanks for this work in any case, looking forward to it being merged! |
|
@Robinlovelace Good news, you don't need this change to set shortcuts; they are already customizable with plain text files. See this article for details: https://support.rstudio.com/hc/en-us/articles/206382178-Customizing-Keyboard-Shortcuts |
|
Great, thanks @jmcphers ! I guess setting Rmd chunks to evaluate in the console (not inline is what I meant) still requires this change? |
|
Yes, that's correct. |
|
|
|
There's an overview in the PR: Later, this will be documented in more detail in the RStudio Server Administration Guide. |
|
Any progress in this enhancement? |
|
@AtomicNess123 It's documented for RStudio Desktop Pro (works the same for the Open Source version AFAICT) and RStudio Workbench née Server Pro. |
We've often had requests to store user preferences in a user-accessible location, using a user-editable file format. The motivation is typically to make it possible to develop a set of personal settings which can be moved from machine to machine, stored on version control, etc.
We currently store most user preferences in a private file inside
~/.rstudio/monitored/user-settings(or the platform equivalent), many of them in a JSONuiPrefsblob. Since RStudio's inception, several editing platforms (Sublime and Visual Studio Code) have exposed their preferences as user-editable JSON. We could do the same with a handful of changes:user-settingscontent into internal settings (including machine-specific settings such ascontextIdentifier) and external settings.user-settingsfile.The text was updated successfully, but these errors were encountered: