From: "Bas V. de Bakker" <bas@astro.uva.nl>
To: zsh-workers@math.gatech.edu
Subject: Re: 2.6b13 history question
Date: Wed, 21 Feb 1996 09:34:23 +0100 [thread overview]
Message-ID: <199602210834.DAA00014@euclid.skiles.gatech.edu> (raw)
In-Reply-To: Wayne Davison's message of Tue, 20 Feb 1996 11:41:49 -0800
Wayne Davison <wayne@soprano.clari.net> writes:
> While I like the lack of added spaces, I don't like the fact that
> hist_ignore_space doesn't strip (non essential) double and trailing
> spaces. I would like to see this option restored.
It never did such a thing. The hist_ignore_space option makes
commands lines starting with a space not appear in the history list.
It did and still does. The fact that those spaces you mention were
removed had nothing to do with this option.
Bas.
prev parent reply other threads:[~1996-02-21 8:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-02-17 22:35 Jeff Blank
1996-02-19 9:12 ` P.Stephenson
1996-02-19 17:57 ` Zefram
1996-02-20 19:41 ` Wayne Davison
1996-02-21 8:34 ` Bas V. de Bakker [this message]
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=199602210834.DAA00014@euclid.skiles.gatech.edu \
--to=bas@astro.uva.nl \
--cc=zsh-workers@math.gatech.edu \
/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).