Each one will wait for a completion message before opening the next pane. Here is my example script for starting multiple services in iTerm2, each on their On a laptop, sometimes there is not enough CPU power to boot up everything simultaneously. This rules out port clash problems, synchronisation conflicts, etc. I needed to actually wait for each server to print its “ready/listening” messageīefore moving on to the next one. Unfortunately, most examples I found on the web using the iTerm2 PythonĪPI started everything in parallel. Just for anyone else tracking this, Nathan joined from There are awesome process monitors like PM2 to help manage multiple services, butįully-dockerized workflows and place them in separate panes for easy log monitoring. We do have just one process in daemon mode, but a number of things can start additional processes (the simplest being Super+I) Not sure if the shutdown process sends SIGTERM to processes so they can do a sane shutdown. It would be a relatively easy shortcut to add. (I think the vte encryption key is thrown away when exiting.)Ģ?) We don't have a nuclear quit option at the moment. Of course there was a hoo-ha when it was discovered that the vte widget was saving the session log into /tmp without encryption (it now encrypts) so should we also have to encrypt this info? Sensitive detail stored? How do we persist across separate sessions? If we have a defined key, then someone can find that and read your files anyway. Perhaps we can grow indefinitely, (although saving it would slow the exit down as this was retrieved from the /tmp/ that vte uses for scrollback, then saved to a file) and only truncate when the user uses the terminal reset which clears the buffer. Where there was some interesting thoughts exchanged on how we could persist things like per terminal history (commands run, not the output) 1) We still need to handle someone setting infinite scrollback. Just for anyone else tracking this, Nathan joined from https:/ /answers. But for the usual case where the user's homedir is on local storage I don't think it should be too problematic. NFS storage and if the network is lossy you don't want terminator to slow to a crawl as a result. I believe this should be a setting because the user's homedir might be on e.g. Perhaps an additional setting to continuously sync scrollback history to disk in case of unexpected termination. Note that Stephen's proposal above will not address your use case because it only covers clean exit. But for the usual case where the user's homedir is on local storage I don't think it should be too Boddy If for some reason I want to close all Terminator windows at once without shutting down the computer I can just send it SIGTERM or something, I guess (see Wilkins What if I just leave Terminator open when I shut down? Even though I have three windows open right now I note that there is one terminator process running, so you wouldn't have to worry about IPC coordination. I was wondering if there would be problems with multiple windows. Seems reasonable to restrict that file to the same number of lines to solve the unbounded growth problem. (Can it be done direct? Or use "cat"? How to grey out? Or draw a horizontal line?)ġ) Terminator has a setting for number of scrollback lines. I guess it would be in three parts:ġ) On exit save the scrollback buffer to somewhere like ~/.cache/ terminator/ $_buffer.out (How to prevent it forever growing?)Ģ) On load push the saved cache file into the vte widget. Would be somewhere between tricky and impossible. Possibly a keyboard shortcut for those that want it? I don't think I'd want it enabled or in the menu by default, because it's somewhat of a nuclear option. This would need thought, because if you have multiple windows in your layout/session, right now there is no way to exit the whole layout/session. Theoretically it should be possible to add a check box in the layout pane to save session on exit. (Some of these bits might only be in trunk. Save layout information (position, size of terminals)Īre all saved when saving layouts.
0 Comments
Leave a Reply. |