-
Notifications
You must be signed in to change notification settings - Fork 29
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
Removing the tab binary after an upgrade breaks the running tab daemon #163
Comments
Hi @userxfce, Removing the I think there are a few things that can be improved here:
I also have an item on the backlog (#44) to shut down the daemon when the tab binary changes, but I've been holding off on implementing it because I'm worried about conflicting installations (e.g. both cargo and homebrew) causing weird behavior with daemon shutdowns. |
The tab daemon should monitor it's own executable, as well as the tab runtime directory. If the file doesn't exist, it should trigger a global shutdown. |
In 0.4.0, there are incompatibility warnings for two cases (added in #180).
Both warning messages recommend I decided against auto-shutdown if the tab executable is removed because existing tabs still work in this case - and those tabs may have local servers, ssh sessions, etc. |
After having run "tab --install all", and then "tab -shutdown", now running "tab" no longer hangs. |
Closing, v0.4.0 is released! |
under xubuntu 20.04 terminal (bash, also rxvt, gnome-terminal), "tab foo" hangs
workaround: removing ~/.tab/ and reinstalling via "tab --install all" solves it
The text was updated successfully, but these errors were encountered: