Skip to content
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

[Feature] Let the user change .workspacefolder #437

Open
dantearaujo1 opened this issue Apr 23, 2023 · 3 comments
Open

[Feature] Let the user change .workspacefolder #437

dantearaujo1 opened this issue Apr 23, 2023 · 3 comments

Comments

@dantearaujo1
Copy link
Contributor

So, i started to use workspace, but i save all my configs file in a specific folder managed by git. I don't know a better way to manage all the configs files of my programs other than that, i would like to set a an user enviroment variable to move .workspacer folder in C:\Users...... to this folder that is located in D: drive. I could make a PR if u want! Just issuing here to know what are your thoughts about this feature. Thanks!

@josteink
Copy link
Member

I've done something similar to Emacs, and on Windows you can't really have symlinks.

What I did for emacs (and for other software too) was just to chain-load the git-hosted configuration by having a simple config which just loads/includes the git hosted one by pointing to a fixed path.

Not sure if csharp-scripts has an include-feature, or if we would then have to "invent" it ourselves?

@josteink
Copy link
Member

Looking into it, it seems like there is a #load-directive which may be used to solve that need?

https://learn.microsoft.com/en-us/archive/msdn-magazine/2016/january/essential-net-csharp-scripting

image

@jshield
Copy link

jshield commented May 31, 2023

you can junction directories on windows, but I don't know if that will work with workspacer

otherwise, if you are managing your dot files in a repo, you could use a powershell script to install them in the correct location whenever you do a git pull with githooks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants