From: Andrej Borsenkow <borsenkow.msk@sni.de>
To: Wayne Davison <wayne@clari.net>
Cc: Peter Stephenson <pws@ifh.de>,
Zsh hackers list <zsh-workers@math.gatech.edu>
Subject: Re: hist_strip_spaces (was Re: histignoredups done properly)
Date: Tue, 13 Aug 1996 09:48:56 +0400 (MOW) [thread overview]
Message-ID: <Pine.SV4.3.95.960813094337.21931B-100000@itsrm1> (raw)
In-Reply-To: <199608121917.MAA03396@bebop.clari.net>
On Mon, 12 Aug 1996, Wayne Davison wrote:
> Peter Stephenson writes:
> > This fixes histignoredups so that only lines which are really
> > different are stored; insignificant changes in whitespace are not
> > treated as differences.
>
[ snipped ]
> Since it may be that not everyone will want this, I made it depend on a
> new option, HIST_STRIP_SPACES. I haven't modified the documentation yet,
> however.
>
The idea is really nice. Here is another one:
I often find itself in a position, where I use several command in a loop;
e.g. (simplified)
% vi
% cc
% ./a.out
or like. What about "HIST_IGNORE_ALL_DUPS" option, which would keep only
globally unique command line? It would be very easy to add this (now it
shold probably be combined with strip_spaces as well).
Any comments?
greetings
-------------------------------------------------------------------------
Andrej Borsenkow Fax: +7 (095) 252 01 05
SNI ITS Moscow Tel: +7 (095) 252 13 88
NERV: borsenkow.msk E-Mail: borsenkow.msk@sni.de
-------------------------------------------------------------------------
prev parent reply other threads:[~1996-08-13 6:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-08-12 12:56 histignoredups done properly Peter Stephenson
1996-08-12 19:17 ` hist_strip_spaces (was Re: histignoredups done properly) Wayne Davison
1996-08-12 21:13 ` hist_strip_spaces Wayne Davison
1996-08-13 9:22 ` hist_strip_spaces Wayne Davison
1996-08-13 5:48 ` Andrej Borsenkow [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=Pine.SV4.3.95.960813094337.21931B-100000@itsrm1 \
--to=borsenkow.msk@sni.de \
--cc=pws@ifh.de \
--cc=wayne@clari.net \
--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).