rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Byron Rakitzis <byron@rakitzis.com>
To: rc@hawkwind.utcs.toronto.edu, tjg@star.le.ac.uk
Subject: Re: non login "rc" needs customized environment
Date: Tue, 26 Feb 2002 19:52:23 -0500	[thread overview]
Message-ID: <200202270052.g1R0qNS28877@rakitzis.com> (raw)

Okay, here's a suggestion.

What if by default a non-interactive rc executes .rcrc, but it does so
implicitly with the -n flag set.

Then, we need a builtin to be able to turn off -n, so that the non-
interactive portions of .rcrc might be interpreted.

Finally, there also then needs to be a mechanism for avoiding the infinite
recursion of .rcrc's.

An example .rcrc:

	#
	# Non-interactive stuff goes here
	#
	exec +n		# made-up builtin

	path=(/a/bin /b/bin /c/bin)

	#
	# Interactive stuff goes here
	#
	exec -n		# made-up builtin

	stty dec

It's convoluted because I want rc to preserve compatability with the
old .rcrc semantics:

i.e., I want an old .rcrc to work properly even via rsh.

Maybe this is a holy grail not worth pursuing since who likes the
old semantics of rsh anyway?

Byron.


             reply	other threads:[~2002-02-27  2:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-27  0:52 Byron Rakitzis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-27  6:29 Byron Rakitzis
2002-02-27  6:26 Russ Cox
2002-02-15  4:11 Byron Rakitzis
2002-02-15 14:04 ` Tim Goodwin
2002-02-27  1:46   ` callum.gibson
2002-02-27  2:16     ` Chris Siebenmann
2002-02-27 13:32       ` Carlo Strozzi
2002-02-27 13:29   ` Carlo Strozzi
2002-02-27 22:24     ` Matt H
2002-02-27  6:13 ` Derek Fawcus
2002-02-14 17:44 Byron Rakitzis
2002-02-15  0:18 ` Dave Mason
2002-02-15  3:21 ` Scott Schwartz
2002-02-14 13:35 Smarasderagd
2002-02-15  0:37 ` Greg A. Woods
     [not found] <chet@nike.ins.cwru.edu>
2002-02-13 20:36 ` Chet Ramey
2002-02-14  2:16   ` Scott Schwartz
2002-02-14 23:35     ` Markus Friedl
2002-02-15  3:05       ` Scott Schwartz
2002-02-13 19:21 Peter Koch

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=200202270052.g1R0qNS28877@rakitzis.com \
    --to=byron@rakitzis.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
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).