From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21014 invoked by alias); 17 Jun 2015 00:15:56 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 35499 Received: (qmail 21643 invoked from network); 17 Jun 2015 00:15:55 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.0 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version:content-type; bh=XDafOTrze2OZPdmpgKYVSGCgbP3fve1ajel5jDM6WOI=; b=VCfVfI+tfcXqNVyPrQ9Mxn2BAhJCAIn4W95O8xlRKuT1oSWfwZLTUr8r0MbCflWiTs LzdxJTlckEVK0JBqdBIu/YWCxpP/MSILQE8zVU3L4b3Ec+bik4Mihf4GZWG2hngvqYuy DVQsXl8A011cnRapycoqp3uZmXPUPpbJ8Q+rbuZDFi1EXH69TjGpb+Z2uQSMhQ0ivssb 7pj0BMRy8jlZn5LcKlQfMs73xYJEoUVVA4DuWUyUWHq71gcfGf200m8aYD6Nu0xCi/PV bemD/s6a1MlCzajotR0SgL7sc1l8PXw2uMP/gmyS/mcYVP9pKtfeESVsZdqgxlFV5pr3 uJ4Q== X-Gm-Message-State: ALoCoQnOtOClwd6zuZ02wCkB382OgYHSNh9V9Ao0cGxvOK351zOz8tOMpXa47wemHSemE7ZYAhKH X-Received: by 10.202.168.85 with SMTP id r82mr2236609oie.55.1434500153068; Tue, 16 Jun 2015 17:15:53 -0700 (PDT) From: Bart Schaefer Message-Id: <150616171549.ZM28192@torch.brasslantern.com> Date: Tue, 16 Jun 2015 17:15:49 -0700 In-Reply-To: <26384.1434494110@thecus.kiddle.eu> Comments: In reply to Oliver Kiddle "Re: PATCH: muddled completion search status" (Jun 17, 12:35am) References: <23493.1434450587@thecus.kiddle.eu> <26384.1434494110@thecus.kiddle.eu> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Zsh workers Subject: Re: PATCH: muddled completion search status MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Jun 17, 12:35am, Oliver Kiddle wrote: } } I wrote: } > There's a further feature where if you press Ctrl-S (or whatever) again, } > it will restore the last search string used. This feature is also } > triggered if your next key is that for a reverse search. } } After checking, I noticed that this is exactly the same for history } incremental search. Again, I think it is better not to restore the } previous search string if the search direction has changed. Unless I misunderstand you, repeating a search in emacs searches again for the last-searched-for string no matter which direction the new search is going. The same is true for vi's "n" or "N" command for searching again up/downward. Why do you think it's wrong to restore the last search string? I would prefer not to break similarity (I won't go so far as to say "compatibility") with emacs in this regard. So maybe I'm just not following what you mean.