-
Notifications
You must be signed in to change notification settings - Fork 206
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
Will there be a devcontainer open
command?
#30
Comments
We want to keep this new CLI independent of VS Code, so an |
That seems to make sense... when I looked at other proposed solutions to make VS Code & the CLI easier I got the impression that the image IDs might not match what VS Code's "Open Folder in Container..." would do. Do you think that is un-warranted? I have not confirmed if it was the case or not. Also, did y'all have thoughts on where |
I think an Initially, it could support vscode only. More editors could be added over time. Or even an generic implementation could also be added so that any editor can plug-in without having to be supported by |
There's several hacks using This definitely should have better support. Until I found that hack, I stayed on the version provided by the vscode-remote extension, which is rather buggy to say the least. |
I was getting kind of tired of opening a new VS Code window and using the "Remote-Containers: Open Folder in Container..." command and was wondering if there was an easy way to do the same via the CLI. Eventually I stumbled on this thread which I've participated on as well.
microsoft/vscode-remote-release#2133 (comment)
Not sure if this project would have a simple
open
command or not or where that would land?The text was updated successfully, but these errors were encountered: