From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-29211-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 7203 invoked by alias); 10 May 2011 05:08:16 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 29211
Received: (qmail 4613 invoked from network); 10 May 2011 05:08:14 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
Received-SPF: pass (ns1.primenet.com.au: SPF record at _spf.google.com designates 74.125.83.171 as permitted sender)
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=
MIME-Version: 1.0
Sender: 4wayned@gmail.com
In-Reply-To: <BANLkTimsaZNtZ_uqr+S-QzV2B8v7nGGanA@mail.gmail.com>
References: <BANLkTinNiXnaHb2mWJhWOKZoqoE9U1Bhcw@mail.gmail.com>
	<BANLkTi=EypRYYfDn9JjBxhB5aHZWkf8VsA@mail.gmail.com>
	<BANLkTimsaZNtZ_uqr+S-QzV2B8v7nGGanA@mail.gmail.com>
Date: Mon, 9 May 2011 22:08:07 -0700
X-Google-Sender-Auth: 7rVbIvgeVk9wtkz-fK-3L5j0ryQ
Message-ID: <BANLkTikZ7NCNMXDPwxayBF3wykkMnmP3pg@mail.gmail.com>
Subject: Re: PATCH: (rfc) HIST_FIND_DUPS option
From: Wayne Davison <wayned@users.sourceforge.net>
To: Mikael Magnusson <mikachu@gmail.com>
Cc: zsh workers <zsh-workers@zsh.org>
Content-Type: multipart/alternative; boundary=bcaec5215eb10ae69704a2e4f106

--bcaec5215eb10ae69704a2e4f106
Content-Type: text/plain; charset=UTF-8

On Mon, May 9, 2011 at 5:03 PM, Mikael Magnusson <mikachu@gmail.com> wrote:

> Yeah, but why show it again if there was an intervening other line, but not
> otherwise?
>

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.

..wayne..

--bcaec5215eb10ae69704a2e4f106--