-
Notifications
You must be signed in to change notification settings - Fork 215
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything else looks good.
@scsmithr Would it make sense to also have an |
That seems sensible but this PR is fine on its own. Should make an issue |
Thank you for the PR, but #34 is easily implemented and will categorically solve this problem. |
Wouldn't it make sense to have some sane defaults? These two would probably cover most use cases |
It's unclear which path to use when both exist. I have VS Code insiders installed right now but I don't actually use it, so this change would silently break sshcode for me. |
I think @ammario 's concern can be solved if we keep the selected version to be used in a config file may be. |
@SscSPs I'm wary of requiring an additional file just to specify where the configuration dir is. That sounds a bit like a catch 22. Using environment variables, or at the very least CLI flags, would be much cleaner and wouldn't deviate from the standard configuration of code-server or Code. |
We could potentially prompt users if both are found, and remember on consecutive runs |
Imho doing that would be too much cli interaction when our goal is to provide a GUI text editor over SSH... |
Agreed with @foresthoffman that a configuration file is plain overkill. A selection prompt doesn't feel very unixey to me. Will open a PR for the environment variable solution. |
762aec5
to
bf1da12
Compare
is it better now? |
You can integrate this PR into #39 |
Don't you think that having two ways of doing the same thing is bad UX? |
IMHO the environment variables should be used only if vscode/vscode-insiders is not installed in the default path |
closing this to make way for #40 |
Add a flag for using extensions and settings from VSCode Insiders