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 guess it's up to you and your application, you may have difficulty checking whether wrongshell exists though as you'll need to check the $PATH (and also source .bashrc/.zshrc etc. as appropriate).
For VS Code we just output it in the panel but then immediately close the panel and show the exit code of the shell process. It's a pretty bad experience right now but it's better than doing nothing.
@Tyriar yeah actually I needed this to resolve this issue, cause right now the window is just being closed without any notice. I guess the best will be displaying a warning or something like that.
Very similar to the VS Code problem, right now I listen to see if the terminal exits within 500ms of launching and if so, I assume it crashed due to the config. Not perfect but a good stop gap solution until something better is implemented.
What is the best way to handle errors? For example if I got the following code:
The line
console.log(data)
is gonna printexecvp(3) failed.: No such file or directory
because the shellwrongshell
doesn't exist.Is it better to check if the shell exists before initializing pty? Or is there any error handling built in to handle this type of errors?
The text was updated successfully, but these errors were encountered: