From: Moritz Neeb <neeb@kpvn.de>
To: sup-talk@rubyforge.org
Subject: [sup-talk] ncursesw encoding
Date: Wed, 24 Nov 2010 18:54:29 +0100 [thread overview]
Message-ID: <4CED5155.3080502@kpvn.de> (raw)
Hello everyone,
William Morgan wrote:
[sup-talk] System encoding versus messages encoding
Tue Apr 22 19:18:00 EDT 2008
> The good news is that I've just made it slightly simpler, at least if
> you're running from git. I've published an "ncursesw" branch that
> contains a hacked ncurses-0.9.1 and a dirty script to install it into
> your ../lib/ directory. If you use that AND you run from git next,
> you'll see wide characters. It works!
>
> So, just a "few" "simple" commands:
> $ git branch --track ncursesw origin/ncursesw
> $ git checkout ncursesw
> $ cd ncurses-0.9.1/
> $ ./run-this-for-sup.sh
> $ cd ..
> $ git checkout next
> $ ruby -Ilib bin/sup
>
> ... and you should see wide characters, assuming your terminal is
> capable. If make dies, you probably need to install some kind of
> ncursesw development library. On my Debian system it's
> a package called libncursesw5-dev.
Is the suggested approach up to date? I am not really into git stuff,
but I think the "next" repository is not in a state, that the commands
below have the same effect than they had two years ago. Can you help me,
to get this working? Is there another approach to get the
message-encoding correctly displayed?
--
Moritz Neeb
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2010-11-24 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 17:54 Moritz Neeb [this message]
2010-11-24 19:09 ` Tero Tilus
2010-11-25 11:51 ` Moritz Neeb
2010-11-25 13:50 ` Tero Tilus
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=4CED5155.3080502@kpvn.de \
--to=neeb@kpvn.de \
--cc=sup-talk@rubyforge.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