From: Rich Lane <rlane@club.cc.cmu.edu>
To: Richard Heycock <rgh@topikality.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] sent mail
Date: Fri, 09 Apr 2010 18:09:56 -0400 [thread overview]
Message-ID: <1270850674-sup-4940@zyrg.net> (raw)
In-Reply-To: <1270731588-sup-6397@roughage.com.au>
I switched the dependency back to plain ncurses because ncursesw was
failing to compile on unusual platforms (because of its wide
characterness). I guess this calls for a ncurses-new gem based on the
same upstream code as ncursesw but without the wide character support.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-04-09 22:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 10:08 Neil Stewart
2010-04-08 12:01 ` Richard Heycock
2010-04-08 12:54 ` Neil Stewart
2010-04-08 13:27 ` Richard Heycock
[not found] ` <alpine.DEB.1.10.1004092231370.4476@stewart.warwick.ac.uk>
2010-04-09 21:37 ` Neil Stewart
2010-04-09 22:09 ` Rich Lane [this message]
2010-04-14 13:06 ` William Morgan
2010-04-08 21:44 ` Neil Stewart
-- strict thread matches above, loose matches on Subject: below --
2010-04-06 14:13 Neil Stewart
2010-04-06 16:23 ` Michael Stapelberg
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=1270850674-sup-4940@zyrg.net \
--to=rlane@club.cc.cmu.edu \
--cc=rgh@topikality.com \
--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