From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11086 invoked from network); 27 Apr 2008 00:27:40 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.4 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 27 Apr 2008 00:27:40 -0000 Received-SPF: none (ns1.primenet.com.au: domain at sunsite.dk does not designate permitted sender hosts) Received: (qmail 76656 invoked from network); 27 Apr 2008 00:27:35 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 27 Apr 2008 00:27:35 -0000 Received: (qmail 24821 invoked by alias); 27 Apr 2008 00:27:30 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 24884 Received: (qmail 24802 invoked from network); 27 Apr 2008 00:27:28 -0000 Received: from bifrost.dotsrc.org (130.225.254.106) by sunsite.dk with SMTP; 27 Apr 2008 00:27:28 -0000 Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.169]) by bifrost.dotsrc.org (Postfix) with ESMTP id 36365808A38A for ; Sun, 27 Apr 2008 02:27:24 +0200 (CEST) Received: by wf-out-1314.google.com with SMTP id 25so3958904wfc.3 for ; Sat, 26 Apr 2008 17:27:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=twf75Prrcp1bKfpKUuknC0bUerDQRPi6gJDfv/TUNnA=; b=rB+/joageRBad5eh72fdDcO0TayC+U6Aja9tdBj2h93C2lMgYxU2SyjaGvp4mJlcBOxNqEQqxU4vSPAE91hpMUQLarprBUneswGSpctoJdIid4rB9JuPnQH6JChT6GFeVSxtxEecVKWSq42BjLbIhwS9srzMW6i0UZbWh+x4xys= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ecX11ycT5sXvXq8Qu9/VZfk7IKI1h9mN2LM+RcZSqabBKr+C/VogOx+DPauCcFsi1sBMsxcTLUrpDwt+jBA8+vTwlpH7JssbjvdfGmjmeowyrm8njVyHg/jBTn5dGftFKXCUuSoAK9FJjO4RRXIVWjot0aNMXAPWDSUpJtJjadA= Received: by 10.143.33.19 with SMTP id l19mr878900wfj.18.1209256043014; Sat, 26 Apr 2008 17:27:23 -0700 (PDT) Received: by 10.142.142.12 with HTTP; Sat, 26 Apr 2008 17:27:22 -0700 (PDT) Message-ID: <17393e3e0804261727s560acff7sb6125d8f8b46b4b4@mail.gmail.com> Date: Sat, 26 Apr 2008 20:27:22 -0400 From: "Matt Wozniski" To: zsh-workers@sunsite.dk Subject: Re: PATCH: isearch match highlighting In-Reply-To: <4827.1209250119@pws-pc> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4827.1209250119@pws-pc> X-Virus-Scanned: ClamAV 0.91.2/6957/Sat Apr 26 20:28:22 2008 on bifrost X-Virus-Status: Clean On Sat, Apr 26, 2008 at 6:48 PM, Peter Stephenson wrote: > This one is worth posting. > > With pattern matching in isearch, it's now quite useful to have the > matched string highlighted. I've made the default underlining rather > than standout because of the annoyance that standout on a cursor that's > shown in inverse video flips it to normal video, then when you've just > matched one character there's nothing at all on the line. This seems to > be common behaviour. > > You could argue that if highlighting is done this way it would make more > sense for the cursor position to be where the user is typing, but I > it's non-trivial to change, hard to be sure the highlighting selected is > going to work, incompatible with usage when there's no highlighting, and > I don't feel like monkeying with it anyway. > > I can't help feeling I must have screwed up this one somehow. Is this working for others? It doesn't seem to work at all for me. zsh -f bindkey -e ^Rb and the shell goes into a tight loop, using 100% of one of my cores, and won't die to anything less than a kill -9. Anybody else see this? It's a fresh checkout, built with './configure --enable-multibyte --with-term-lib=ncurses' ~Matt