rc-list - mailing list for the rc(1) shell
 help / color / Atom feed
From: Paul Haahr <paul@paulhaahr.com>
To: Tim Goodwin <tjg@star.le.ac.uk>
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: rc 1.6 $version
Date: Wed, 3 Apr 2002 10:06:47 -0500
Message-ID: <cZGNG75Vn2@dmul.paulhaahr.com> (raw)
In-Reply-To: <20020403143130.22327.qmail@happy.star.le.ac.uk>

Tim wrote

> > I'd prefer $rc-version, but either should be fine.
> 
> (As it turns out, this is all irrelevant, but I have would two
> objections to this.  First, `-' turns on free careting, [...]

Yeah, I forgot about that.  (We had fixed that in es.)

> Secondly, rc is meant to be C-ish, not Lisp-ish.)

That, too, we fixed in es.

> Mea culpa.  I failed to realise that there are two types of special
> variable in rc: 1) those that merely have a default initial value, and
> 2) those that invoke special code when substituted.  Till now,
> $version was in category 2.  I've just moved it to category 1.

This seems quite sensible.

> As a separate matter, several variables are not exportable.  These
> are: $apid, $apids, $cdpath, $home, $ifs, $path, $pid, and $*.
> (Remember that $cdpath, $home, and $path are all aliased to upper case
> versions, which *are* exportable.  Also, the default assignment to
> $path happens before $PATH is examined: so if $PATH is set, $path will
> acquire its value instead of the default.)
> 
> I think $bqstatus and $status ought to be non-exportable too.  I've
> just made them so; you can all see what this breaks in the next
> release candidate :-).

Seems good to me.

Three questions:
  - Is $version exportable?
  - Is $version exported if the user doesn't assign to it?
  - Is $version inherited from the environment?

--p


  reply index

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-14 22:37 erik quanstrom
2002-03-27 13:27 ` Tim Goodwin
2002-03-27 21:12   ` Carlo Strozzi
2002-03-30 18:43     ` Paul Haahr
2002-03-31 15:13       ` Carlo Strozzi
2002-04-03 14:31       ` Tim Goodwin
2002-04-03 15:06         ` Paul Haahr [this message]
2002-04-04 10:04       ` Tim Goodwin
2002-04-04 21:42         ` Scott Schwartz
  -- strict thread matches above, loose matches on Subject: below --
2002-04-05  1:38 smarry
2002-04-04 21:54 Byron Rakitzis
2002-04-05  8:35 ` Tim Goodwin
2001-10-23 21:32 Beta release rc-1.6b3 available Carlo Strozzi
2001-10-24  3:34 ` Chris Siebenmann
2001-10-24  8:04   ` Carlo Strozzi
     [not found] <sroberts@certicom.com>
2001-10-23 15:55 ` Sam Roberts
2001-10-23 21:14   ` Scott Schwartz
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
2001-10-23  7:55 ` Carlo Strozzi
2001-10-23 12:44   ` Tim Goodwin
2001-10-23 15:47   ` Markus Friedl
2001-10-23 21:09     ` Carlo Strozzi
     [not found] <tell@cs.unc.edu>
2000-05-08 23:25 ` building rc on QNX4 Stephen Tell
2000-05-10  0:37   ` builtins Scott Schwartz
2000-05-12  7:22     ` builtins Carlo Strozzi
2000-05-04 15:18 building rc on QNX4 Carlo Strozzi
2000-05-08  8:29 ` Tim Goodwin
     [not found]   ` <tjg@star.le.ac.uk>
2000-05-08 11:50     ` David Luyer
2000-05-08 13:28   ` Carlo Strozzi
2000-04-27 17:39 Carlo Strozzi
2000-05-02 14:41 ` Tim Goodwin
2000-04-27 16:56 Scott Schwartz
2000-04-27 20:41 ` Sam Roberts
2000-04-28  7:28   ` vrl (was: Re: building rc on QNX4) Gert-Jan Vons
2000-04-28 18:38     ` Sam Roberts
2000-05-02  8:16       ` Gert-Jan Vons
2000-04-28 19:03     ` rc not session leader? Sam Roberts
2000-04-26 15:02 building rc on QNX4 Sam Roberts
1997-09-18 23:26 are there any patches which add ~ expansion to rc Chris Siebenmann
     [not found] ` <cks@hawkwind.utcs.toronto.edu>
1992-06-04 10:05   ` $pid malte
1992-11-04 12:45   ` set subtract malte
1992-11-06 12:03   ` rc and signal handlers malte
1997-09-19 17:21   ` are there any patches which add ~ expansion to rc Jeremy Fitzhardinge
2001-10-24  3:25   ` Beta release rc-1.6b3 available Chris Siebenmann
2001-10-24  3:41     ` Scott Schwartz
1997-09-17 15:56 are there any patches which add ~ expansion to rc Joseph Skinner
1997-09-17 21:56 ` Scott Schwartz
1997-09-17 22:08 ` Mark K. Gardner

Reply instructions:

You may reply publically 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=cZGNG75Vn2@dmul.paulhaahr.com \
    --to=paul@paulhaahr.com \
    --cc=rc@hawkwind.utcs.toronto.edu \
    --cc=tjg@star.le.ac.uk \
    /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

rc-list - mailing list for the rc(1) shell

Archives are clonable: git clone --mirror http://inbox.vuxu.org/rc-list

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.archive.rc-list


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git