rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Sam Roberts <sroberts@certicom.com>
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: Beta release rc-1.6b3 available
Date: Tue, 23 Oct 2001 10:55:02 -0500	[thread overview]
Message-ID: <20011023105502.A28670@certicom.com> (raw)
In-Reply-To: <20011023085557.A16410@texne.com>

I'd like to second this. It's the only reason I don't use rc as my
shell, other than that I really like it. Does anybody have a patch?


Quoting Carlo Strozzi <carlos@scriptaworks.com>, who wrote:
> Mine is not really a bug report, buth rather a request for a new
> feature. I dunno whether it has been asked before on this list, but
> are there any chances that rc will ever handle a path specification
> in the form of:
> ; command ~/path/to/file
> where ``~'' gets substituted internally with the value of $home ?
> Likewise, ~user should be replaced by $home/user/. Of course this
> is a-la-bash, but it would make rc much more handy to use as
> a login shell. The executable that I use has been linked with the
> GNU readline library, which handles the above cases correctly, but
> when it passes the path to rc the latter complains, of course.

Sam Roberts <sroberts@certicom.com>

  parent reply	other threads:[~2001-10-23 19:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-15 13:56 Tim Goodwin
2001-10-17 14:13 ` Buggs
2001-10-17 14:34   ` Tim Goodwin
2001-10-17 21:13     ` Buggs
     [not found] ` <20011019004843.A429@gc.wirefire.com>
2001-10-19 17:14   ` Tim Goodwin
2001-10-22  6:47     ` Scott Schwartz
2001-10-24  3:25       ` Chris Siebenmann
2001-10-24  3:41         ` Scott Schwartz
2001-10-23  7:55 ` Carlo Strozzi
2001-10-23 12:44   ` Tim Goodwin
2001-10-23 21:32     ` Carlo Strozzi
2001-10-24  3:34       ` Chris Siebenmann
2001-10-24  8:04         ` Carlo Strozzi
2001-10-23 15:47   ` Markus Friedl
2001-10-23 21:09     ` Carlo Strozzi
2001-10-23 15:55   ` Sam Roberts [this message]
2001-10-23 21:14     ` Scott Schwartz
2001-10-26 23:57 Gary Carvell

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20011023105502.A28670@certicom.com \
    --to=sroberts@certicom.com \
    --cc=rc@hawkwind.utcs.toronto.edu \


* 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).