Subject: [sup-talk] ncursesw encoding

From: Moritz Neeb <[email-masked]>
Date: Wed, 24 Nov 2010 18:54:29 +0100

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
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: Moritz Neeb <[email-masked]>
Date: Thu, 25 Nov 2010 12:51:27 +0100

Tero Tilus wrote:
> Moritz Neeb, 2010-11-24 19:54:
>> Is there another approach to get the 
> Did you try installing ncursesw gem?

Yes, I installed it via 'gem install ncursesw', but it is not detected 
by sup: "No 'ncursesw' gem detected ..."

btw: I installed sup as a debian package, not as gem. Could this be a 
problem?

---

From: Tero Tilus <[email-masked]>
Date: Thu, 25 Nov 2010 15:50:21 +0200

Moritz Neeb, 2010-11-25 13:51:
> I installed sup as a debian package, not as gem. Could this be a 
> problem?

I don't know.  Though I wouldn't be surprised if it turns out to be.
Rubygems and Dpkg provide essentially the same service (package and
dependency management) and are (afaik) not aware of each other.  As a
result they do not play together at all.  Usually there are no
collisions but ymmv.

On Debian derivatives my route of least gray hair has been to install
Rubygems from sources using defaults and as much of the Ruby stuff
from gems as possible.

--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: Tero Tilus <[email-masked]>
Date: Wed, 24 Nov 2010 21:09:44 +0200