Unknown option --goto

[alanhg]

Is there a mistake in the way it is used?

/usr/bin/code-server --auth none --goto /root/a.json@5:5

version info

code-server 4.8.3 977b853

[alanhg]

@jsjoeio

Do you know the issue?

[jsjoeio]

In my notes, that's what I did 🤔 Can you try that and report back? I may need to update release notes and changelog

[alanhg]

[jsjoeio]

I can't tell but from the screenshot it looks like you're running that from within code-server or a VS Code Integrated Terminal. Is that right?

Here I do it outside and it works:

Screen.Recording.2022-12-05.at.9.53.10.AM.mov

Try this: VSCODE_IPC_HOOK_CLI= code-server --auth none -r /root/a.json:2:3

OH actually wait...I just tried like you too. I think the code-server -r assumes you already have a running instance going so I don't think it will work like that 🤔 You'd have to do code-server --auth none and then later do code-server -r <file>. I don't know if that's considered a bug or not 🤔 cc @code-asher

[code-asher]

Oh oops yeah looks like we made a typo in the release notes. No need for a new flag. I think in VS Code it is a separate flag which is why we got confused.

Yeah, this is how it works by design. The idea is that you spawn code-server as a system service that way it is always running in the background then -r will always try to connect to it and error if it is not up.

We could make -r spawn code-server if it has not spawned yet but it is kind of a weird scenario to be in because code-server is designed as a daemon and not a one-off process.

Also we plan on removing our code around this and calling Code's server CLI directly which has the same behavior so if we fix it now we would have to port those changes upstream somehow or maintain a patch.

Still, if the behavior is confusing enough maybe we make the change anyway.

[code-asher]

Whatever we do, we should really improve that error. ENOENT is not terribly helpful.