From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: Startup files
Date: Tue, 20 Apr 1999 09:33:29 -0700 [thread overview]
Message-ID: <990420093329.ZM3000@candle.brasslantern.com> (raw)
In-Reply-To: <9904160751.AA36373@ibmth.df.unipi.it>
On Apr 16, 9:51am, Peter Stephenson wrote:
} Subject: Startup files
}
} It's probably not too late to alter GLOBAL_RCS_FIRST into something else
Agreed. (In fact, sort of by definition there's nothing new in 3.1.x
that we can't alter, but in practice I suppose anything pre-3.1.4 is
pretty much locked in.)
} What would be the preferred strategy? Test NO_RCS before every script
} apart from /etc/zshenv, and skip them if it's set? Does this meet
} everybody's requirements?
Semantically, that would do it for me. However, I wonder if it's going
to cause any problems ... I don't imagine anyone sets NO_RCS just to
turn off the logout files, but it's possible.
Maybe the right thing is a new flag that could be set in ~/.zshenv to
disable only the (remaining) global files. The sysadmin still gets
his shot in /etc/zshenv, and thereafter it's simple for the user to
get back control and keep it.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1999-04-20 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-16 7:51 Peter Stephenson
1999-04-20 16:33 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-05-30 19:10 Bernd Eggink
1997-05-31 4:43 ` Geoff Wing
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=990420093329.ZM3000@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.auc.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).