From: Vincent Lefevre <vincent@vinc17.org>
To: zsh-users@sunsite.dk
Subject: Re: [4.0.2 bug] commands not written to history
Date: Thu, 12 Jul 2001 14:43:17 +0200 [thread overview]
Message-ID: <4a98ea1d71vincent@vinc17.org> (raw)
In-Reply-To: <1010712033003.ZM31613@candle.brasslantern.com>
On 12 Jul, Bart Schaefer <schaefer@candle.brasslantern.com> wrote:
> Hrm. Just because there's an entry in $HISTFILE doesn't mean that it's
> present in the shell history, of course. With INC_APPEND_HISTORY set
> (as I believe you have), $HISTFILE may have up to $[SAVEHIST/5] extra
> commands stored in it. (This is to avoid having to rewrite the entire
> file too frequently.) But only $HISTSIZE of those commands is actually
> in memory (and thus searchable) at any given time.
But this wasn't the problem, as the history contained about 100 lines
(it was just after I used a new history file), and $HISTSIZE is 2000
here.
> Next time you see this happen, try running `fc -W temphistfile' and then
> `diff $HISTFILE temphistfile'. You should see differences only at the
> beginning and possibly one or two commands at the end, not in the middle.
> If there are commands missing (or misordered) in the middle, then we'll
> have evidence of a real bug.
greux:~[Failed 130]> fc -W temphistfile <14:30:51
greux:~> diff $HISTFILE temphistfile <14:35:11
112c112
< : 994936533:0;mail
---
> : 994937129:867;mail
116,120c116,119
< : 994939941:0;m $HISTFILE
< : 994939999:0;mail
< : 994940004:0;m $HISTFILE
< : 994940081:0;mail
< : 994940743:0;rem
---
> : 994939966:13;m $HISTFILE
> : 994939999:2;mail
> : 994940004:8;m $HISTFILE
> : 994940743:308;rem
122d120
< : 994941319:0;diff $HISTFILE temphistfile
Is it normal?
It seems that a "mail" command has disappeared from the history file.
> } It seems to be due to the fact that the time stamps are not in the
> } increasing order.
> Can you show an example of this, please?
This can be done by manually copying commands to the history file
(useful when starting with a new history file...). But even without
doing that:
[...]
: 994850317:0;emacs cshrc.loria
: 994850342:0;rl lepois
: 994850341:0;locale
[...]
But this is because host lepois wasn't synchronized, so a very special
case.
--
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/> - 100%
validated HTML - Acorn Risc PC, Yellow Pig 17, Championnat International des
Jeux Mathématiques et Logiques, TETRHEX, etc.
Work: CR INRIA - computer arithmetic / SPACES project at LORIA
next prev parent reply other threads:[~2001-07-12 12:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-29 14:33 Vincent Lefevre
2001-06-29 15:50 ` Bart Schaefer
2001-06-29 18:14 ` Vincent Lefevre
2001-06-30 16:06 ` Bart Schaefer
2001-07-02 10:42 ` Vincent Lefevre
2001-07-11 22:34 ` Vincent Lefevre
2001-07-11 23:59 ` Vincent Lefevre
2001-07-12 3:30 ` Bart Schaefer
2001-07-12 12:43 ` Vincent Lefevre [this message]
2001-07-12 17:46 ` Bart Schaefer
2001-07-12 20:38 ` Vincent Lefevre
2001-07-12 20:58 ` Wayne Davison
2001-07-13 18:07 ` Bart Schaefer
2001-08-07 19:46 ` Wayne Davison
2001-08-07 20:39 ` Vincent Lefevre
2001-07-21 13:44 ` Vincent Lefevre
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=4a98ea1d71vincent@vinc17.org \
--to=vincent@vinc17.org \
--cc=zsh-users@sunsite.dk \
/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).