From: Scott Schwartz <schwartz@bio.cse.psu.edu>
To: Byron Rakitzis <byron@rakitzis.com>
Cc: pk@TechFak.Uni-Bielefeld.DE, rc@hawkwind.utcs.toronto.edu
Subject: Re: non login "rc" needs customized environment
Date: Thu, 14 Feb 2002 22:21:29 -0500 [thread overview]
Message-ID: <20020215032129.14309.qmail@g.bio.cse.psu.edu> (raw)
In-Reply-To: Message from Byron Rakitzis <byron@rakitzis.com> of "Thu, 14 Feb 2002 12:44:05 EST." <200202141744.g1EHi5I04374@rakitzis.com>
| This behavior with rsh has always been a problem -- csh gets around
| it with .cshrc, and I wonder if some similar solution might be necessary
| for backward compatability.
Take a look at what zsh does. There are lots of cases one might
want to handle, once you start in with different config files:
STARTUP/SHUTDOWN FILES
Commands are first read from /etc/zshenv. If the RCS option
is unset within /etc/zshenv, all other initialization files
are skipped. Otherwise, commands are read from
$ZDOTDIR/.zshenv. (If ZDOTDIR is unset, HOME is used
instead). If the first character of argument zero passed to
the shell is -, or if the -l flag is present, then the shell
is assumed to be a login shell, and commands are read from
/etc/zprofile and then $ZDOTDIR/.zprofile. Then, if the
shell is interactive, commands are read from /etc/zshrc and
then $ZDOTDIR/.zshrc. Finally, if the shell is a login
shell, /etc/zlogin and $ZDOTDIR/.zlogin are read.
| I love the SHLVL hack, but if you put it in place, then rc will now
| process .rcrc differently across different versions of the shell, and
| I'd prefer some backward compatability if at all possible.
SHLVL leaves me cold. The issue is how to tell a shell to do some
initialization---nesting level should be conceptually infinite, and
shouldn't effect that.
next prev parent reply other threads:[~2002-02-15 3:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 17:44 Byron Rakitzis
2002-02-15 0:18 ` Dave Mason
2002-02-15 3:21 ` Scott Schwartz [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-27 0:52 Byron Rakitzis
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 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=20020215032129.14309.qmail@g.bio.cse.psu.edu \
--to=schwartz@bio.cse.psu.edu \
--cc=byron@rakitzis.com \
--cc=pk@TechFak.Uni-Bielefeld.DE \
--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).