Zsh Mailing List Archive
Messages sorted by:
Re: idea for new feature (was: Re: sticky-note and zle bindings)
- X-seq: zsh-users 12901
- From: "Robert Knight" <robertknight@xxxxxxxxx>
- To: zsh-users@xxxxxxxxxx
- Subject: Re: idea for new feature (was: Re: sticky-note and zle bindings)
- Date: Sat, 7 Jun 2008 05:39:40 +0100
- In-reply-to: <20080128163340.GA18831@xxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <080125095733.ZM20873@xxxxxxxxxxxxxxxxxxxxxx> <080124215848.ZM19758@xxxxxxxxxxxxxxxxxxxxxx> <2d460de70801250149t360f9938u18d458b03f464c72@xxxxxxxxxxxxxx> <1B47D24854C7BC4FA8DA28BEBB59B0BA02E64EAC@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <2d460de70801260729q34fb7ed8o11446e63a320b2ad@xxxxxxxxxxxxxx> <13ed09c00801251018l1007ac9an9c453651d5695c46@xxxxxxxxxxxxxx> <080125181227.ZM21172@xxxxxxxxxxxxxxxxxxxxxx> <2d460de70801260741q16e4f197he2307be6e4f81c82@xxxxxxxxxxxxxx> <080126153143.ZM6173@xxxxxxxxxxxxxxxxxxxxxx> <20080128163340.GA18831@xxxxxxxxx>
I'd like to implement my part of this quite soon. So here is a more
(1) The terminal emulator creates a unique alphanumeric ID string for each
new session and passes it to the shell as an environment variable
When the shell is killed via a SIGHUP it saves that state and the
associated session ID.
When restoring that session, the terminal emulator starts a new
instance of the shell as
usual, with the previously used $SHELL_SESSION_ID value. The shell
looks for state saved
under that name and restores the previous state. If no state is saved
against the id then
the shell can assume that it is a new session. The ID would be
alphanumeric, with no fixed
length or format. I would probably use Qt's UUID generator to come up
with something suitable
but users might choose human-readable names if they wanted to do their
own session management.
(2) The terminal emulator specifies a file for the shell to save its
to. If the file is empty or does not exist then the shell assumes
this is a new session. Otherwise it restores the contents of the
file. The save/restore handling then works as in (1).
I favour the first option because the shell can pick a suitable place
to store its
state information which is in the same location/format as the rest of
its data. Unlike a filename, an ID also works over remote
Policies over exactly what gets saved and restored and how long that
information should be kept for would be left up to the shell to begin
I can make suggestions about what would be most useful however,
roughly in priority order.
The real gist is to minimize the time spent doing repetetive setup
routines to prepare for
working on various tasks.
- Environment variables (probably not the complete environment but
rather a delta between
the environment inherited by the shell when it started and the
environment in the shell when
it was closed)
Digging back through my mail from users, something which would earn
much love from sysadmins
would be if they could save the state of their terminal, with 10-20
connections to various
machines via SSH and later restore that again instantly - including as
much state as possible
on the remote end.
2008/1/28 Andy Spiegl <zsh.Andy@xxxxxxxxx>:
> On 2008-01-26, 15:31, Bart Schaefer wrote:
>> } Restoring the programs that ran is a very interesting idea. I like it :)
>> Not "the programs that ran". The programs that *were running*; that is,
>> something the shell had to SIGHUP when it exited. I'd be very leery of
>> automatically restarting anything other than the foreground job, though,
>> and maybe not even that if it was a pipeline.
> I really like the idea of restoring the program that was running
> before the "crash", but I'd suggest not to reexecute it (which may
> have fatal side effects) but just putting it on the command line.
> The user can then decide whether to press enter or not.
> Once you've seen one shopping center you've seen a mall.
Messages sorted by: