From: Mikael Magnusson <mikachu@gmail.com>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] EXTENDED_HISTORY documentation typo
Date: Thu, 27 Oct 2011 21:13:30 +0200 [thread overview]
Message-ID: <CAHYJk3Q3J8S4GObfuF7hto9pqBNyxrFRei-7RJC5TW1tFDyzwQ@mail.gmail.com> (raw)
In-Reply-To: <111027115013.ZM19042@torch.brasslantern.com>
On 27 October 2011 20:50, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Oct 27, 6:12pm, Mikael Magnusson wrote:
> } Subject: Re: [PATCH] EXTENDED_HISTORY documentation typo
> }
> } % history -dD
> } 1 18:06 0:00 HISTFILE=/tmp/test
> } 2 18:06 0:00 HISTSIZE=50
> } 3 18:06 0:00 SAVEHIST=50
> } 4 18:06 0:00 setopt incappendhist
> } 5 18:06 0:00 setopt incappendhistory
> } 6 18:06 0:00 cat /tmp/test
> } 7 18:06 0:00 setopt extendedhistory
> } 8 18:06 0:00 cat /tmp/test
> } 9 18:06 0:05 sleep 5
> } 10 18:07 0:00 cat /tmp/test
> }
> } At first i thought maybe it's one of my local patches, but i get the
> } same result on a remote host running 4.3.10.
>
> This is exactly what I'd expect. Zsh doesn't even bother storing the
> time delta if extended history isn't set. Hence you get the delta
> at event 9 after having set the option at event 7.
>
> There isn't a HIST_REVISIONIST option. :-)
Hm? I ran the sleep after I did setopt extendedhistory. Note also that
the time delta 0:05 is output by history -dD but isn't stored in the
history file. You didn't quote the histfile excerpt:
setopt extendedhistory
: 1319731616:0;cat /tmp/test
: 1319731618:0;sleep 5
: 1319731624:0;cat /tmp/test
--
Mikael Magnusson
next prev parent reply other threads:[~2011-10-27 19:13 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
2011-10-27 16:12 ` Mikael Magnusson
2011-10-27 18:50 ` Bart Schaefer
2011-10-27 19:13 ` Mikael Magnusson [this message]
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=CAHYJk3Q3J8S4GObfuF7hto9pqBNyxrFRei-7RJC5TW1tFDyzwQ@mail.gmail.com \
--to=mikachu@gmail.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).