From: Vin Shelton <acs@alumni.princeton.edu>
To: Mikael Magnusson <mikachu@gmail.com>
Cc: "zsh-users@zsh.org" <zsh-users@zsh.org>
Subject: Re: Saving commands from a session
Date: Tue, 20 Jan 2015 14:33:35 -0500 [thread overview]
Message-ID: <CACeGjnVd1htv-FHNjpAbTZSsxkJ2A6MOgokYZMNNUJUmVWHxoA@mail.gmail.com> (raw)
In-Reply-To: <CAHYJk3RLO_bOg4MOfRWNYffxuSiM6=d4MBQP4eEJLzMcTrAAJA@mail.gmail.com>
On Mon, Jan 12, 2015 at 12:19 PM, Mikael Magnusson <mikachu@gmail.com> wrote:
> On Mon, Jan 12, 2015 at 6:01 PM, Vin Shelton <acs@alumni.princeton.edu> wrote:
>> In addition to saving commands in .zhistory, I like to save commands
>> by session, so I can save and later search the sequence of commands I
>> executed at a particular time. In order to do this, in .zlogout I
>> compared all commands in history against the date and time of the
>> first command saved:
>>
>> # Get the date and time of the first command in the shell history.
>> fc -lin -$HISTCMD -$((HISTCMD-1)) | read d t cmd
>>
>> # Ignore all commands that have the same date and time.
>> # They were read in when the shell started.
>> fc -lin -$HISTCMD | grep -v "^$d $t" >> $outfile
>>
>> I was never terribly impressed by the elegance of this solution, but
>> it worked, more or less (I believe it could drop the first command or
>> two I entered if they happened to have the same date and time as the
>> start of the shell).
>>
>> However, I recently started using
>>
>> setopt EXTENDED_HISTORY
>>
>> and this has the effect of keeping the original date and time the
>> command was executed in .zhistory, so when the historical commands are
>> read into the shell, they no longer all have the same date and time.
>>
>> Is there a more elegant way to save only those commands that have been
>> executed in this instance of the shell?
>
> Maybe you want to write out each entry incrementally from
> zshaddhistory() instead? Zsh does track which history entries are
> "local" and which are imported from history, but I don't believe you
> can directly access this information.
Thanks, Mikael. I followed your advice and am now using zshaddhistory().
Regards,
Vin
prev parent reply other threads:[~2015-01-20 19:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 17:01 Vin Shelton
2015-01-12 17:19 ` Mikael Magnusson
2015-01-20 19:33 ` Vin Shelton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACeGjnVd1htv-FHNjpAbTZSsxkJ2A6MOgokYZMNNUJUmVWHxoA@mail.gmail.com \
--to=acs@alumni.princeton.edu \
--cc=mikachu@gmail.com \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).