Zsh Mailing List Archive
Messages sorted by:
Re: PATCH: (rfc) HIST_FIND_DUPS option
- X-seq: zsh-workers 29211
- From: Wayne Davison <wayned@xxxxxxxxxxxxxxxxxxxxx>
- To: Mikael Magnusson <mikachu@xxxxxxxxx>
- Subject: Re: PATCH: (rfc) HIST_FIND_DUPS option
- Date: Mon, 9 May 2011 22:08:07 -0700
- Cc: zsh workers <zsh-workers@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=YuEwz2rpjkWyB77qelvywb2mlb032Xwg9EDmWXcZaQY=; b=ZcshSYdumhWvQm9X7yq0X+oOBwg6JN+oG+BJ6VZ1g3sk7SUd5tDhj/yriXpm6PQy2w xeEfrOLipJn/k5iBp3I7ZIUgCH6YsSEjMBhu/ZAD3IX/LDpGOiSdiZ5dTZdsI8hZFR9y VhM4j3rIcgEHO9n1HVNPS6M6oOfeH44n6UWUk=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=HLsZBPMIAGl3lwQDH34wuvTQ79G+D03DNtGKB5wxFFgC53tN6ChxCf8HWB9CURNLs7 MsXMWwJv2StW/Tf7Lux/hQwFnaC5CjEgCRAIsm35kT9YPTrEKbCqROBJFtXTBlK5bHJG F4gGXDhqtHyE5032tfCGcGn1+UBjH4sQBcHrs=
- In-reply-to: <BANLkTimsaZNtZ_uqr+S-QzV2B8v7nGGanA@mail.gmail.com>
- List-help: <mailto:firstname.lastname@example.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:email@example.com>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <BANLkTinNiXnaHb2mWJhWOKZoqoE9U1Bhcw@mail.gmail.com> <BANLkTi=EypRYYfDn9JjBxhB5aHZWkf8VsA@mail.gmail.com> <BANLkTimsaZNtZ_uqr+S-QzV2B8v7nGGanA@mail.gmail.com>
- Sender: 4wayned@xxxxxxxxx
On Mon, May 9, 2011 at 5:03 PM, Mikael Magnusson <mikachu@xxxxxxxxx> wrote:
> Yeah, but why show it again if there was an intervening other line, but not
Well, that's the whole purpose of the no-dups option is to remove all the
duplicates that you've already rejected. With that off, zsh just tries to
avoid appearing to be buggy -- if the user hits a key to search backward and
the line doesn't change, it has the appearance of having done nothing.
This is already possible, and indeed how I have been using this feature.
Nice! I had forgotten that post.
Unfortunately I don't think I can do anything from this hook to affect the
> dupness of results.
It might be interesting to have a way for that hook to affect the value of
last_line so that it could not compare as identical.
One more note on your idea of a HIST_FIND_ALL_DUPS option -- it would need
to affect other hist movement too. I know that the arrow up/down code has a
similar avoid-the-appearance-of-doing-nothing idiom, for instance.
Messages sorted by: