From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Peter Stephenson <pws@ibmth.df.unipi.it>,
zsh-users@sunsite.auc.dk (Zsh users list)
Subject: Re: Reading initialization/logout files again.
Date: Mon, 31 May 1999 05:39:30 +0000 [thread overview]
Message-ID: <990531053930.ZM1092@candle.brasslantern.com> (raw)
In-Reply-To: <9905231441.AA28756@ibmth.df.unipi.it>
(I feel a bit odd being the poster of ten consecutive zsh-workers article
numbers and several more on zsh-users, but I'm still catching up after my
system downtime.)
On May 23, 4:41pm, Peter Stephenson wrote:
} Subject: Reading initialization/logout files again.
}
} This was some discussion about this before.
In fact, very far before. Start at
http://www.zsh.org/cgi-bin/mla/redirect?WORKERNUMBER=488
(yes, four hundred eighty-eight) and work your way up the references links.
} I'm not sure why NO_RCS behaves the way it does at the moment; it may be so
} that the administrator can unset it in /etc/zshenv
Also note that in the thread around zsh-workers/1414, Zoltan ignored me when
I repeatedly asked why NO_RCS works the way it does.
} The latest proposal to allow more flexibility as follows:
}
} - The NO_RCS option (or negated RCS option) remains as before
}
} - A new NO_GLOBAL_RCS [...] will determine whether the /etc/z* files are
} sourced at any stage.
}
} - The previously proposed option GLOBAL_RCS_FIRST would be removed.
}
} There are alternatives, however:
}
} 1. [...] make the NO_RCS option more
} flexible and allow it to determine the subsequent behaviour at any stage
}
} 2. [...] make NO_GLOBAL_RCS work just like NO_RCS, except that
} it applies to files in /etc only and is tested just after .zshenv is run.
All three of these suggestions (latest, #1, #2) are OK. I slightly prefer
alternative #1, and slightly dislike alternative #2.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
prev parent reply other threads:[~1999-05-31 5:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-23 14:41 Peter Stephenson
1999-05-31 5:39 ` Bart Schaefer [this message]
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=990531053930.ZM1092@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=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).