From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Arch utf8 vs UTF-8 fix and wide character support
Date: Tue, 11 May 2010 15:19:43 -0400 [thread overview]
Message-ID: <1273605454-sup-2267@masanjin.net> (raw)
In-Reply-To: <k2l6242182a1005111150n1b018aanf8a939e1d260b59a@mail.gmail.com>
Reformatted excerpts from Matti Eiden's message of 2010-05-11:
> I don't know what is the opinion of other sup users, whether adding a
> new dependency (to terminfo) is desirable, as the current list of
> dependencies is already rather high.
I'm working on a gem that provides both wcswidth functionality and the
ability to slice a string at specific display widths, both of which, I
think, will be required to function entirely.
You can try it with 'gem install console'. It's 1.9-only for now.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-05-11 19:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <y2j6242182a1005061059w5e32fb54vd10ccfd7e4a1911e@mail.gmail.com>
2010-05-06 18:02 ` Matti Eiden
2010-05-07 16:46 ` Rich Lane
2010-05-11 18:50 ` Matti Eiden
2010-05-11 19:19 ` William Morgan [this message]
2010-05-11 21:51 ` Matti Eiden
2010-05-13 12:33 ` William Morgan
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=1273605454-sup-2267@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-devel@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