From: bachjh@googlemail.com (Jörg-Hendrik Bach)
Subject: [sup-talk] ncurses-ruby-1.2.3 + ncursesw hack breaks search
Date: Wed, 01 Jul 2009 17:42:04 +0200 [thread overview]
Message-ID: <1246462442-sup-1884@BlackMesa> (raw)
In-Reply-To: <1246437271-sup-7636@cannonball>
Ingmar Vanhassel, Wed Jul 01 10:38:36 +0200 2009:
> Has anyone noticed that newer versions of ncurses-ruby plus that
> ncursesw hack [1] (to link to ncurses with widechar support) breaks search?
I can confirm the behaviour.
> When I search for 'foo', sup launches a search for a bunch of weird
> characters, not for 'foo', which obviously returns nothing useful.
True. However, with the following workaround, you can get proper search results:
- search for foo -> garbled search, no proper results
- hit 'x' to destroy the result buffer
- hit '\' to search again.
- hit uparrow to go to previous search. backspace all the garbled characters there.
- repeat the uparrow + remove until it shows your last working search (or until there's no more previous search to go to)
- type foo again, hit enter: works.
Not that this is the type of thing you'd want to do for a simple search. Guess we'll have to wait for ruby 1.9?
cheers,
- J?rg-Hendrik
>
> I can trigger this with ncurses-ruby 1.2.2, 1.2.3. Version 1.1 seems to
> be unaffected.
>
> [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477366#52
prev parent reply other threads:[~2009-07-01 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 21:39 [sup-talk] Character encoding when displaying quoted-printable messages Jim Cheetham
2009-07-01 5:20 ` Jim Cheetham
2009-07-01 8:38 ` [sup-talk] ncurses-ruby-1.2.3 + ncursesw hack breaks search Ingmar Vanhassel
2009-07-01 15:28 ` William Morgan
2009-07-01 15:42 ` Jörg-Hendrik Bach [this message]
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=1246462442-sup-1884@BlackMesa \
--to=bachjh@googlemail.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox