Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: benoit.pierre@gmail.com (Benoît PIERRE)
Subject: [sup-talk] ncurses hack
Date: Tue, 18 Aug 2009 20:59:20 +0200	[thread overview]
Message-ID: <1250621614-sup-5683@localdomain> (raw)
In-Reply-To: <1250620908-sup-7463@archpc>

Excerpts from Dusan's message of Tue Aug 18 20:46:52 +0200 2009:
> Excerpts from Beno?t PIERRE's message of Tue Aug 18 20:24:45 +0200 2009:
> > Excerpts from Dusan's message of Tue Aug 18 09:42:48 +0200 2009:
>
> [...]
> 
> I will, just give me day or two. I am using gem version, not svn or git.
> I did some stuff with them but never with ruby. Can you give me two
> lines help what to install and where? Latest svn?

You can probably directly patch the sources in the gem. For example on
Ubuntu, the sources should be somewhere in /var/lib/gems/1.8/gems/sup-xxx.

Use 'gem environment' to get the installation directory.

Another option is to follow the wiki to get the latest git version:
http://sup.rubyforge.org/wiki/wiki.pl?Contributing
-- 
A: Because it destroys the flow of conversation.
Q: Why is top posting dumb?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090818/302eaeb0/attachment.bin>


  reply	other threads:[~2009-08-18 18:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-17 19:54 Edward Z. Yang
2009-08-18  2:43 ` William Morgan
2009-08-18  7:42   ` Dusan
2009-08-18 18:24     ` Benoît PIERRE
2009-08-18 18:46       ` Dusan
2009-08-18 18:59         ` Benoît PIERRE [this message]
2009-08-18 19:04           ` Dusan
2009-08-18 19:24           ` Dusan
2009-08-18 19:31       ` Jörg-Hendrik Bach

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=1250621614-sup-5683@localdomain \
    --to=benoit.pierre@gmail.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