From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] EXTENDED_HISTORY documentation typo
Date: Thu, 27 Oct 2011 08:57:18 -0700 [thread overview]
Message-ID: <111027085718.ZM18523@torch.brasslantern.com> (raw)
In-Reply-To: <CAHYJk3SVKOhEZMz7xCqKvCb6CjZoahQenr3-__sfeG3Z4vr74Q@mail.gmail.com>
On Oct 27, 3:51pm, Mikael Magnusson wrote:
}
} When I enable extendedhistory and run a command for a few seconds (in
} the foreground), the <elapsed seconds> field is always 0.
Hrm.
torch% history -dD
1 08:09 0:00 setopt extendedhistory
2 08:12 0:30 sleep 30
torch% SAVEHIST=50
torch% fc -W /tmp/ehist
torch% cat /tmp/ehist
: 1319728176:0;setopt extendedhistory
: 1319728336:30;sleep 30
: 1319729722:0;history -dD
: 1319729869:0;SAVEHIST=50
(Timestamps are a bit far apart because I was distracted by phone call
while doing this).
Here's a thing ... if you're using a zshaddhistory hook to store lines
to the history with "print -s" or "print -S", the start time of the
command is lost and consequently so is the elapsed time; print forces
the start and end times of the entry it writes to both be the time of
the call to print.
There may be a similar issue with HIST_IGNORE_ALL_DUPS in that the times
for the oldest duplicate are kept, whereas HIST_EXPIRE_DUPS_FIRST keeps
those of the most recent duplicate.
next prev parent reply other threads:[~2011-10-27 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 23:59 Simon Ruderich
2011-10-27 13:51 ` Mikael Magnusson
2011-10-27 15:57 ` Bart Schaefer [this message]
2011-10-27 16:12 ` Mikael Magnusson
2011-10-27 18:50 ` Bart Schaefer
2011-10-27 19:13 ` Mikael Magnusson
2011-10-28 14:28 ` Bart Schaefer
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=111027085718.ZM18523@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@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).