From: Vincent Lefevre <vincent@vinc17.org>
To: zsh-users@sunsite.dk
Subject: [4.0.2 bug] commands not written to history
Date: Fri, 29 Jun 2001 16:33:49 +0200 [thread overview]
Message-ID: <20010629163348.A9632@greux.loria.fr> (raw)
I sometimes write related commands like
$ cmd1
$ cmd2
And several hours/days later, I can recall cmd1 from the history and
type ^O to recall cmd2 automatically. I don't want to do that in a
script or in a function, to have full control on these commands (and
be able to insert commands between cmd1 and cmd2 if need be).
But sometimes (difficult to say under which conditions), a copy of cmd1
had been written to the history (as expected), but there is no copy of
cmd2. That is, ^O gives me another command (instead of cmd2).
Here are my history options:
greux:~> setopt|grep hist <16:29:44
extendedhistory
histignoredups
histignorespace
histnofunctions
histnostore
histreduceblanks
incappendhistory
greux:~> unsetopt|grep hist <16:29:46
noappendhistory
nobanghist
cshjunkiehistory
histallowclobber
nohistbeep
histexpiredupsfirst
histfindnodups
histignorealldups
histsavenodups
histverify
sharehistory
I reported a similar problem for zsh 3.1.9 in November (message-id of
the first mail: <20001129141451.A24159@lepois.loria.fr>). And I got a
reply saying:
--------
IIRC, this bug was fixed back in July:
2000-07-17 Wayne Davison <wayned@users.sourceforge.net>
* 12265: Src/hist.c: Fixed gethistent().
In the case you cite, the gethistent() function would sometimes fail when
called from savehistfile().
--------
I don't know if this is related...
--
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 reply other threads:[~2001-06-29 14:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-29 14:33 Vincent Lefevre [this message]
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
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=20010629163348.A9632@greux.loria.fr \
--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).