From: bachjh@googlemail.com (Jörg-Hendrik Bach)
Subject: [sup-talk] sup and ncursesw
Date: Sat, 13 Jun 2009 16:17:51 +0200 [thread overview]
Message-ID: <91de50e10906130717x3a6d6097g5249ed6bb17fbfcf@mail.gmail.com> (raw)
In-Reply-To: <1244836517-sup-5520@entry>
2009/6/12 William Morgan <wmorgan-sup at masanjin.net>
>
> What is your environment's character set? (Should be the first line of
> output logged by Sup.) What is your terminal emulator? And what's the
> behavior without the patch to ncurses.so?
After playing around a bit i think the behaviour might be related to a
problem with locale.
I reinstalled ruby, rubygems, ncurses and sup. No patch to ncurses this
time. Using gnome-terminal or xterm with "TERM=xterm" now lets umlauts etc
look like, e.g. "JM-CM-6rg-Hendrik"). The reported character set is "utf8".
The same happens when using urxvt with TERM=rxvt-unicode.
However, calling sup like this:
$ LC_ALL=en_GB.iso-8859-15 sup
results in different behaviour in the two emulators: xterm looks OK when
viewing the inbox, but inserts boxed question marks in thread-view.
rxvt-unicode displays everything correctly, but drops the last character of
a line when a non-ASCII element is somewhere in the line. In both variants
sup reports the character set correctly as iso-8859-15.
So I guess I could simply work in urxvt and that's OK, then.
Do other widechar ncurses programs work?
The only other ncurses-based program I am aware of using is midnight
commander, and it seems to be working fine. But I don't know whether it uses
the widechar variant.
cheers,
- J?rg-Hendrik
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090613/c8c73902/attachment.html>
next prev parent reply other threads:[~2009-06-13 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 17:50 Jörg-Hendrik Bach
2009-06-12 20:03 ` William Morgan
2009-06-13 14:17 ` Jörg-Hendrik Bach [this message]
2009-06-15 14:04 ` William Morgan
2009-06-17 16:14 ` William Morgan
2009-06-18 9:26 ` 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=91de50e10906130717x3a6d6097g5249ed6bb17fbfcf@mail.gmail.com \
--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