not opening folder when exec in dot directory

[mikebarkmin]

When code . is executed in a dot directory like .config code will not be able to open the folder by itself. It will just started with an empty page complaing that .config is a directory and cannot be opened.

I am not sure if it is a vscode bug or a bug in this script.

[owtaylor]

Hmm, I don't see the ".config is a directory and cannot be opened" unless I'm missing the message - I just see an empty vscode window not connected to any directory. (But connected to the container)

It seems to be a visual studio code bug where:

code --remote attached-container+463334 /var/home/otaylor/tmp/.hidden-repo

Doesn't work properly when the argument is a hidden directory, but that's a pretty strange bug! Probably needs some experimentation with vscode not installed as a Flatpak to try and come up with some more minimal reproducer.

[owtaylor]

It seems to be a visual studio code bug where:

code --remote attached-container+463334 /var/home/otaylor/tmp/.hidden-repo

Basically the way this works is that when invoked this way, vscode is guessing whether each argument is a file folder based on the filename before sending it to the remote extension. Visual Studio Code is guessing that ".hidden-repo" is a file because it starts with a dot (Someone once tried to open .zsh_history .... microsoft/vscode-remote-release#3424). You can have problems the other way where it will classify "TODO" as a folder because it doesn't have a dot.

Without the "--remote" argument, vscode looks at the actual type of the argument. We can emulate that by converting the raw path arguments to '--file-uri vscode-remote://...' or '--folder-uri vscode-remote:/...' I'll change things to work that way and hopefully it will be more robust.