Zsh Mailing List Archive
Messages sorted by:
Re: PATCH: (rfc) HIST_FIND_DUPS option
- X-seq: zsh-workers 29210
- From: Mikael Magnusson <mikachu@xxxxxxxxx>
- To: Wayne Davison <wayned@xxxxxxxxxxxxxxxxxxxxx>
- Subject: Re: PATCH: (rfc) HIST_FIND_DUPS option
- Date: Tue, 10 May 2011 02:03:00 +0200
- 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:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=U7o5tVZ3fstjZgxXg55t/Q+TF7DOJfaj9lnmCFqfAV8=; b=A+pEitDR7iFhRNsiJ9tfE6dUvNpg2XgtJR9iTf94x1U7O+a44KX5jaEG5+UaWl2IsK sr20DhBuCyoClyVq0lX0m4x0IclPlEe+Gk9pIevrtS2RAGz1TTUMaDO2fqG0vcWhPFKf 3cmHuBOap7IrNc7TdXilKz22KIapqu4NRTpk4=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=FygPxNjquO71J5A+86TuyS4SlI2iU8CX6XQTapVmAUmLcsVvATDPnb/q25vvHsT+Vs 8GpOZ/zebTA3fhikveJ6NTtb7iv+WX2DQPa/d6W43cnyVxIHiw8Xg3rNANAJ3po/xu47 dQ+8/KJ4a6xHdiU5FSdDWkf76+Cv/HZfABxrk=
- In-reply-to: <BANLkTi=EypRYYfDn9JjBxhB5aHZWkf8VsA@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>
On 10 May 2011 01:51, Wayne Davison <wayned@xxxxxxxxxxxxxxxxxxxxx> wrote:
> On Mon, May 9, 2011 at 3:09 PM, Mikael Magnusson <mikachu@xxxxxxxxx> wrote:
>> I am currently unsure why unsetting HIST_FIND_NO_DUPS doesn't have this
>> behaviour already. Possibly it only finds the same line after finding
>> another line in between that also matches the search
> Exactly. Under normal circumstance, if the user has rejected a particular
> line as not being one that they want to run, showing them the same line
> isn't usually very useful to them (and may indeed be confusing).
Yeah, but why show it again if there was an intervening other line,
but not otherwise?
Ie with this history
searching for foo will give you line 6, 5 and 4, but not 2, then 1. I
just don't see the point of this distinction.
> I don't particularly like the HIST_FIND_DUPS option. If you named it
> HIST_FIND_ALL_DUPS I'd like it a bit better.
Yeah, the name is not set in stone :).
> But I do wonder if there isn't
> a better solution to help you solve this particular search idiom (one where
> you're really searching not just for a line, but for a set of lines). For
> instance, it would be interesting to be able to ask zsh to show a line or
> two of context following the line as you visit each matching line. In such
> a search, it would make a lot of sense to show the user another identical
> line that has differing context, so that would be the default.
This is already possible, and indeed how I have been using this feature.
Unfortunately I don't think I can do anything from this hook to affect
the dupness of results.
Messages sorted by: