From: tom@dbservice.com (Tomas Carnecky)
Subject: [sup-talk] sup on opensolaris
Date: Thu, 30 Jul 2009 20:31:12 +0200 [thread overview]
Message-ID: <C1361ACC-8CF6-4AD9-955C-0B812197AF19@dbservice.com> (raw)
Kids, don't try this at home, it kills kittens! Well, not directly,
but trying to get sup running will drive you so mad you will try to
kill everything that moves. In other words: it doesn't work and the
fact that I'm trying this on opensolaris doesn't make it any easier.
The biggest issue is that the ruby binary from the package manager is
linked against the ancient solaris curses.so but ruby-ncurses needs
ncurses.so (which, to make the issue even more complicated, is in /usr/
gnu/lib). When both libraries are liked into one application, they
don't play along well (=segfaults). I had to compile ruby from source
and make sure it's not liked with curses.so, and also patch ruby-
ncurses slightly. I then managed to get sup to start up and read my
mails. However, there is one issue left that I'm not able to fix:
Ncurses.field.field_buffer() is returning garbage, and that makes is
impossible to write mails, search and set tags etc. The problem is
somewhere inside sup, as the ruby-ncurses example form2.rb is working
just fine (maybe it has something to do with encoding/locale?).
I have an ugly patch for lib/sup/textfield.rb that uses its own string
buffer instead of relying on field_buffer(). It's not perfect, but it
at least allows me to write emails and assign tags.
Other issues:
- strftime("%P") is a GNU extension, I work around this by using
strftime("%p").downcase.
- Iconv.iconv(target + "//IGNORE", charset, text + " ") <- the "//
IGNORE" is causing an InvalidEncoding exception, removing it didn't
seem to cause any regressions
tom
next reply other threads:[~2009-07-30 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 18:31 Tomas Carnecky [this message]
2009-07-31 15:56 ` William Morgan
2009-07-31 16:59 ` Ben Walton
[not found] <1249059559-sup-8960@matrix>
2009-08-04 9:56 ` Tomas Carnecky
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=C1361ACC-8CF6-4AD9-955C-0B812197AF19@dbservice.com \
--to=tom@dbservice.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