zsh-users
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@ibmth.df.unipi.it>
To: zsh-users@sunsite.auc.dk
Subject: Re: zsh startup files
Date: Thu, 25 Mar 1999 12:22:39 +0100	[thread overview]
Message-ID: <9903251122.AA14741@ibmth.df.unipi.it> (raw)
In-Reply-To: "Wolfgang Hukriede"'s message of "Thu, 25 Mar 1999 11:55:41 NFT." <199903251055.LAA02436@sally.ifm.uni-kiel.de>

Wolfgang Hukriede wrote:
> Peter Stephenson <pws@ibmth.df.unipi.it> :
> 
> > To summarise: Invoking zsh -b, or calling `setopt GLOBAL_RCS_FIRST' in
> > /etc/zshenv, would force the order of scripts to be
> >   /etc/zshenv /etc/zprofile /etc/zshrc /etc/zlogin
> >   ~/.zshenv ~/.zprofile ~/.zshrc ~/.zlogin
> > As with the NO_RCS option, setting or unsetting the option at any later
> > point would have no effect.  The sysadmin could force all the global
> > scripts to be used before the user does anything.

(I've sent a patch for this, but the option has to be -d instead of -b,
since that turns out to mean `end of option processing' on the command
line.)

> How about allowing the *user* to `setopt GLOBAL_RCS_FIRST' in their 
> own ~/.zshenv

This makes things rather complicated; there's no fundamental difficulty,
but I'd prefer to keep it clean.  The idea is not that you're at war with
the sysadmin, who's supposed to make it easy for users to set their own
preferences.  But if this is popular enough...

-- 
Peter Stephenson <pws@ibmth.df.unipi.it>       Tel: +39 050 844536
WWW:  http://www.ifh.de/~pws/
Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy


  reply	other threads:[~1999-03-25 11:39 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-24 22:48 Stefan Monnier
1999-03-24 23:15 ` Sweth Chandramouli
1999-03-25  0:47   ` Stefan Monnier
1999-03-25  5:53     ` Sweth Chandramouli
1999-03-25 11:17       ` Doug Morris
1999-03-25  2:20   ` Jason Price
1999-03-25  9:03 ` Peter Stephenson
     [not found]   ` <9903251002.AA18225@ibmth.df.unipi.it>
1999-03-25 10:55     ` Wolfgang Hukriede
1999-03-25 11:22       ` Peter Stephenson [this message]
1999-03-25 12:36         ` Stefan Monnier
1999-03-25 14:00           ` Peter Stephenson
1999-03-25 19:37             ` Stefan Monnier
1999-03-28  1:04               ` Bart Schaefer
1999-03-28 22:14                 ` Stefan Monnier
1999-03-29  1:57                   ` Bart Schaefer
1999-03-29  4:14                     ` Sweth Chandramouli
1999-03-29 14:15                     ` Stefan Monnier
1999-03-29 14:29                       ` Andrej Borsenkow
1999-03-31  7:14                         ` Bart Schaefer
1999-03-31  7:49                           ` Bart Schaefer
1999-04-02 13:12                           ` Stefan Monnier
1999-04-02 17:13                             ` Bart Schaefer
  -- strict thread matches above, loose matches on Subject: below --
2006-03-14 17:38 zzapper
2006-03-14 19:50 ` Wayne Davison
2006-03-15  2:43   ` Bart Schaefer
2006-03-15 18:22     ` Phil Pennock
2006-03-16 19:29     ` Dominic Mitchell
1996-10-19 23:04 Zsh " Nate Johnston
1996-10-20 11:09 ` Zefram

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=9903251122.AA14741@ibmth.df.unipi.it \
    --to=pws@ibmth.df.unipi.it \
    --cc=zsh-users@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).