From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Vincent Lefevre <vincent@vinc17.org>, zsh-users@sunsite.dk
Subject: Re: [4.0.2 bug] commands not written to history
Date: Thu, 12 Jul 2001 03:30:02 +0000 [thread overview]
Message-ID: <1010712033003.ZM31613@candle.brasslantern.com> (raw)
In-Reply-To: <20010712015910.A24326@greux.loria.fr>
On Jul 12, 1:59am, Vincent Lefevre wrote:
} Subject: Re: [4.0.2 bug] commands not written to history
}
} There is another problem. For instance, when I want to backward-search
} for `file.', nothing is found, though there is a matching line in the
} history:
}
} greux:~out> grep "zip -r" $HISTFILE <1:48:28
} : 994891028:0;zip -r file.zip *
} : 994895233:0;grep "zip -r" $HISTFILE
} greux:~out> grep "zip -r" $HISTFILE <1:48:29
} failing bck-i-search: file._
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.
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.
} 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?
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-07-12 3:30 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 [this message]
2001-07-12 12:43 ` Vincent Lefevre
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=1010712033003.ZM31613@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=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).