You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The home folder is populated by the vscode-R folder containing all the data for the extension, with the main drawback of cluttering it.
Describe the solution you'd like
Following the XDG specification (more readable version of the spec in the arch wiki article)
is a very popular and generally recommended way to handle program related configuration, cache, and data.
Describe alternatives you've considered
I am not entirely sure what the contents of the directory are. There's also the possibility of just moving the entire folder into one somewhat appropiate XDG folder such as XDG_DATA_HOME or XDG_STATE_HOME and just leaving the entire thing there. This solves the annoying folder in the home directory and requires, I presume, significantly less development effort.
Additional context
Related issues: #495 is the earliest, citing the spec. Later, #1149, leading to more conversation. It seems there is some consensus around doing this.
For a Windows version of this, this stack overflow answer gives some options, and for MacOS there is this other SO answer, though I do not know their state of affairs.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The home folder is populated by the vscode-R folder containing all the data for the extension, with the main drawback of cluttering it.
Describe the solution you'd like
Following the XDG specification (more readable version of the spec in the arch wiki article)
is a very popular and generally recommended way to handle program related configuration, cache, and data.
Describe alternatives you've considered
I am not entirely sure what the contents of the directory are. There's also the possibility of just moving the entire folder into one somewhat appropiate XDG folder such as XDG_DATA_HOME or XDG_STATE_HOME and just leaving the entire thing there. This solves the annoying folder in the home directory and requires, I presume, significantly less development effort.
Additional context
Related issues: #495 is the earliest, citing the spec. Later, #1149, leading to more conversation. It seems there is some consensus around doing this.
For a Windows version of this, this stack overflow answer gives some options, and for MacOS there is this other SO answer, though I do not know their state of affairs.
The text was updated successfully, but these errors were encountered: