Comment 5 for bug 1257259

Just for anyone else tracking this, Nathan joined from https://answers.launchpad.net/terminator/+question/532791

Where there was some interesting thoughts exchanged on how we could persist things like per terminal history (commands run, not the output) too.

@Nathan: 1) We still need to handle someone setting infinite scrollback. Perhaps we can grow indefinitely, (although saving it would slow the exit down as this was retrieved from the /tmp/<deleted_files> that vte uses for scrollback, then saved to a file) and only truncate when the user uses the terminal reset which clears the buffer. 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. (I think the vte encryption key is thrown away when exiting.)

2?) We don't have a nuclear quit option at the moment. It would be a relatively easy shortcut to add. 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.

Your response to Jeffery is 100% right.