You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the terminal a lot when testing shell functions and stuff. Every now and then it happens that I need to edit a file that is not open in the 834905809345 windows already open but I'm missing a command to tell CodeServer to open the file.
Right now I'm doing a realpath $file and then click on the file in the terminal while holding ctrl.
Having a command like csedit that tells CodeServer via the IPC socket to open the file in the editor would be awesome.
It would be even more awesome If I could pick the split pane where the file would be opened in, like counting from the left, having three split panes: 1,2,3
I'd write something like this:
[cse|csedit|cso|csopen] [1|2|3] filename
cse 2 lib.sh
and the file would be opened in the middle split pane.
What protocol is CodeServer talking on the IPC sockets? Is there documentation about that somewhere?
Cu
The text was updated successfully, but these errors were encountered:
Hi,
I'm using the terminal a lot when testing shell functions and stuff. Every now and then it happens that I need to edit a file that is not open in the 834905809345 windows already open but I'm missing a command to tell CodeServer to open the file.
Right now I'm doing a
realpath $file
and then click on the file in the terminal while holding ctrl.Having a command like csedit that tells CodeServer via the IPC socket to open the file in the editor would be awesome.
It would be even more awesome If I could pick the split pane where the file would be opened in, like counting from the left, having three split panes: 1,2,3
I'd write something like this:
[cse|csedit|cso|csopen] [1|2|3] filename
cse 2 lib.sh
and the file would be opened in the middle split pane.
What protocol is CodeServer talking on the IPC sockets? Is there documentation about that somewhere?
Cu
The text was updated successfully, but these errors were encountered: