From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: PATCH: isearch match highlighting
Date: Sun, 27 Apr 2008 09:48:04 -0700 [thread overview]
Message-ID: <080427094804.ZM29498@torch.brasslantern.com> (raw)
In-Reply-To: <17393e3e0804261727s560acff7sb6125d8f8b46b4b4@mail.gmail.com>
On Apr 26, 8:27pm, Matt Wozniski wrote:
} Subject: Re: PATCH: isearch match highlighting
}
} On Sat, Apr 26, 2008 at 6:48 PM, Peter Stephenson wrote:
} > I can't help feeling I must have screwed up this one somehow.
}
} 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?
I can reproduce this. It's looping in
#0 0x0020fbed in memset () from /lib/tls/libc.so.6
#1 0xbfee0bb0 in ?? ()
#2 0x080c03d0 in mb_metacharlenconv_r (s=0x9783eda "", wcp=0xbfee07d0,
mbsp=0xbfee07b8) at ../../zsh-4.0/Src/utils.c:4008
#3 0x08116720 in doisearch (args=0x8169a1c, dir=-1, pattern=0)
at ../../../zsh-4.0/Src/Zle/zle_hist.c:1408
mb_metacharlenconv_r() is returning 0 on the empty string (which a
comment in utils.c says "probably shouldn't happen") so charpos is
never incremented at line 1412 and the loop at line 1407 never stops.
I think this means end_pos is wrong but I don't have time to try to
chase that back through set_isearch_spot() right now, so we'll have
to wait for PWS.
Note that what's broken is the old history-incremental-search-backward.
Everything works fine with history-incremental-pattern-search-backward.
next prev parent reply other threads:[~2008-04-27 16:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 22:48 Peter Stephenson
2008-04-27 0:27 ` Matt Wozniski
2008-04-27 16:48 ` Bart Schaefer [this message]
2008-04-27 19:57 ` Peter Stephenson
2008-04-28 1:49 ` Matt Wozniski
2008-04-28 9:20 ` Peter Stephenson
2008-04-28 10:50 ` Matt Wozniski
2008-04-28 11:02 ` Peter Stephenson
2008-04-29 17:10 ` Peter Stephenson
2008-04-29 20:12 ` Matt Wozniski
2008-04-29 20:21 ` Matt Wozniski
2008-05-01 10:37 ` Peter Stephenson
2008-05-02 10:49 ` Nikolai Weibull
2008-05-02 11:14 ` Peter Stephenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=080427094804.ZM29498@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).