From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.dk, Vincent Lefevre <vincent@vinc17.org>
Subject: Re: New behaviour for HIST_IGNORE_SPACE option
Date: Tue, 26 Jun 2001 06:24:16 +0000 [thread overview]
Message-ID: <1010626062416.ZM143@candle.brasslantern.com> (raw)
In-Reply-To: <4a8d442eb8vincent@vinc17.org>
[Moved to -workers]
On Jun 19, 11:52pm, Vincent Lefevre wrote:
} Subject: New behaviour for HIST_IGNORE_SPACE option
}
} It seems that the behaviour of HIST_IGNORE_SPACE has changed in
} zsh 4.0.1, and I don't like the new one.
Sorry to have let this languish so long without a reply. We did think
about putting an option in for the old behavior and it's mostly my fault
that there isn't one.
In the course of considering possible workarounds, I discovered that the
new behavior has in fact introduced a few bugs. If you use `print -s'
between commands -- e.g., from precmd, or from completion as happens
with _complete_debug -- while there is a history entry pending space-
deletion, the history becomes garbled: The entry that was added with
`print -s' appears twice, once on either side of the one that should
have been deleted, and the deletion never happens.
It seems to me that `print -s' should simply perform the deletion at
once, replacing the pending entry with the new one.
On a prossibly-unrelated note, `print -s' with no arguments results in
"BUG: attempt to free storage at invalid address" when the next command
is executed:
schaefer[514] print -s
schaefer[517] echo foo
BUG: attempt to free storage at invalid address
foo
schaefer[519] allopt hist
appendhistory on
banghist on
cshjunkiehistory off
extendedhistory off
histallowclobber off
histbeep on
histexpiredupsfirst on
histfindnodups on
histignorealldups off
histignoredups on
histignorespace off
histnofunctions off
histnostore off
histreduceblanks on
histsavenodups off
histverify off
incappendhistory off
sharehistory off
Wayne, are you out there?
--
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 parent reply other threads:[~2001-06-26 6:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4a8d442eb8vincent@vinc17.org>
2001-06-26 6:24 ` Bart Schaefer [this message]
2001-06-28 18:10 ` Wayne Davison
2001-06-30 18:20 ` print -s '' 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=1010626062416.ZM143@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=vincent@vinc17.org \
--cc=zsh-workers@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).