Follow-up Comment #3, bug #44243 (project screen): The user manual at [0] is not up to date. Grab one from the newest source package. It'll be in screen-4.2.1/doc/screen.texinfo .
[0] https://www.gnu.org/software/screen/manual/ I wrote those descriptions and I'm fairly certain I did a poor job of it (suggestions are welcome). They do have to do with splits. A layout tracks how you organize your splits and restores them when you detach and re-attach GNUScreen or even start a fresh GNUScreen. But I kinda agree with mikegerwitz's point of view. What may be confusing is the overloaded use of 'session'. A screen session will let you detach a shell from one terminal and reattach it to a different terminal. But if the underlying shell session dies because because of a reboot, that shell and its environment can't be recreated. For that kind of functionality, it sounds like you need something that will capture and act on a SIGTERM that gets sent on a shutdown. So when onSIGTERM() foreach (process) do { getCWD > ~/archeology_record.txt} or something along those lines. You can do labeling inside GNUScreen. See the commands for :title , :windowlist , and :layout title. You can use :hardstatus for a persistant view of your windows. For dynamic titling, see [1]. Put all of this customization into your ~/.screenrc [1] http://aperiodic.net/screen/title_examples Your .screenrc can also help in automation. One example is at [2]. Take advantage of the (confusingly called) :screen command and :at command, and also look at the -X commandline option [2] http://freecode.com/articles/the-antidesktop HTH _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?44243> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
