From: Taru Karttunen <taruti@taruti.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Ruby Ncurses Bindings
Date: Tue, 16 Feb 2010 15:18:22 +0200 [thread overview]
Message-ID: <1266326246-sup-9743@oz.taruti.net> (raw)
In-Reply-To: <80055d7c1002121906t6e6cbe6cpf6188ddde6e82d3e@mail.gmail.com>
Excerpts from Andrei Thorp's message of Sat Feb 13 05:06:30 +0200 2010:
> For several versions now, sup has shipped with ncurses bindings for
> ruby. I don't understand why they're in there. For my Arch package, I
> delete the ncurses.rb file and allow Sup to use the system-installed
> ruby ncurses bindings instead. Funny enough, they work properly in
> Arch whereas the provided bindings don't. Is there any reason to have
> the bindings in there? Other distros?
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477366
- Taru Karttunen
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2010-02-16 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-13 3:06 Andrei Thorp
2010-02-16 13:18 ` Taru Karttunen [this message]
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=1266326246-sup-9743@oz.taruti.net \
--to=taruti@taruti.net \
--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