rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Tim Goodwin <tgoodwin@cygnus.co.uk>
To: Russell Davies <c9415019@cs.newcastle.edu.au>
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: rc,linux,signal,readline
Date: Tue, 12 Aug 1997 05:42:24 -0400	[thread overview]
Message-ID: <5gYAAAAw8DN3owwA@nan.cygnus.co.uk> (raw)
In-Reply-To: <199708120819.SAA07860@lily.newcastle.edu.au>

>  	I have been trying for a while now to get the following 
>  	working under linux..without success..

Are you using rc1.5b2 and readline 2.1?  Older versions of readline
definitely don't get on with rc...  You can get the latest rc from here.

    ftp://ftp.pipex.net/people/tim/rc-1.5b2.tar.gz

I believe this combination mostly works (although personally I use
editline).  There's a known race condition under Linux which I hope to
fix very soon.

Please let me know if you can't get it working to your satisfaction.

>  	I like some of the features of rc and would like swap shells
>  	completely but if I have to complile statically just for these
>  	simple features, then the difference in size isnt enough to
>  	motivate me to quit using bash.

Which "size" are you trying to economize on?  Shells should
usually be linked statically anyway (see the recent thread on
comp.unix.internals)... for the next release, I'm considering adding
`-static' to the link if we're using gcc.

Tim.


  reply	other threads:[~1997-08-12 20:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-08-12  8:19 rc,linux,signal,readline Russell Davies
1997-08-12  9:42 ` Tim Goodwin [this message]
1997-08-12 13:59 ` rc,linux,signal,readline Tom Culliton
1997-08-12 21:24   ` rc,linux,signal,readline Paul Haahr
1997-08-12 21:55     ` rc,linux,signal,readline Tom Culliton
1997-08-13 13:33       ` rc,linux,signal,readline Tim Goodwin
1997-08-13 14:20         ` rc,linux,signal,readline Tom Culliton
1997-08-13 17:57         ` rc,linux,signal,readline Tom Culliton

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=5gYAAAAw8DN3owwA@nan.cygnus.co.uk \
    --to=tgoodwin@cygnus.co.uk \
    --cc=c9415019@cs.newcastle.edu.au \
    --cc=rc@hawkwind.utcs.toronto.edu \
    /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;
as well as URLs for NNTP newsgroup(s).