From: ingmar@exherbo.org (Ingmar Vanhassel)
Subject: [sup-talk] ncurses-ruby-1.2.3 + ncursesw hack breaks search
Date: Wed, 01 Jul 2009 10:38:36 +0200 [thread overview]
Message-ID: <1246437271-sup-7636@cannonball> (raw)
In-Reply-To: <f4cc59760906302220v1595b4a8xf600a96747d2c408@mail.gmail.com>
Excerpts from Jim Cheetham's message of Wed Jul 01 07:20:10 +0200 2009:
> Nicely fixed by using the hack ncursesw branch, by the way.
> http://sup.rubyforge.org/wiki/wiki.pl?UTF8
Has anyone noticed that newer versions of ncurses-ruby plus that
ncursesw hack [1] (to link to ncurses with widechar support) breaks search?
When I search for 'foo', sup launches a search for a bunch of weird
characters, not for 'foo', which obviously returns nothing useful.
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
--
Exherbo KDE, X.org maintainer
next prev parent reply other threads:[~2009-07-01 8:38 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 ` Ingmar Vanhassel [this message]
2009-07-01 15:28 ` [sup-talk] ncurses-ruby-1.2.3 + ncursesw hack breaks search William Morgan
2009-07-01 15:42 ` Jörg-Hendrik Bach
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=1246437271-sup-7636@cannonball \
--to=ingmar@exherbo.org \
/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