From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Chmouel Boudjnah <chmouel@mandrakesoft.com>
Cc: <cooker@linux-mandrake.com>, Zsh Workers <zsh-workers@sunsite.dk>
Subject: Re: Mandrake 8.0 - compinit in /etc/zshrc
Date: Mon, 21 May 2001 15:50:45 +0000 [thread overview]
Message-ID: <1010521155045.ZM10521@candle.brasslantern.com> (raw)
In-Reply-To: <m31ypi3guy.fsf@giants.mandrakesoft.com>
On May 21, 3:40pm, Chmouel Boudjnah wrote:
}
} and how do you do when you have to modify the skel file on upgrade ?
One possibility might be not to put the code directly into the skel file.
Put it in, say, /etc/zsh.d/compinit. In /etc/zshrc, define a shell
function:
function ZSH_features() {
local feature
for feature in /etc/zsh.d/*(N-.:x)
do
. $feature
done
unfunction ZSH_features
}
Then the skel .zshrc file would contain a block such as:
# BEGIN: Standard zsh feature setup
# This command initializes assorted features that are useful to all
# users. See /etc/zshrc for the definition of this function.
# If you remove this command you may miss new features that are
# added when the zsh packages are upgraded. Edit at your own risk.
typeset +f ZSH_features >/dev/null && ZSH_features
# END: Standard zsh feature setup
Note that Wayne's suggestion is that you add a .zshrc file to the home
directories only of users who don't have one. For users who already do
have one, scan the .zshrc for the BEGIN: line or the ZSH_featues command,
and if it isn't there, do something non-interactive, such as sending them
e-mail, to tell them about the upgrade -- and do that only if their login
shell is set to zsh.
I understand Trond's argument about users with non-local or NFS-shared
directories. It'd be easy enough to skip (or do only the "send e-mail"
step for) the former; for the latter, the `typeset +f' check should
prevent problems if they happen to use zsh on another machine yet for
some reason didn't already have a .zshrc file.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-05-21 15:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-19 18:19 Andrej Borsenkow
2001-05-19 20:26 ` Bart Schaefer
2001-05-19 21:51 ` Wayne Davison
2001-05-20 8:11 ` Andrej Borsenkow
2001-05-20 9:10 ` Wayne Davison
2001-05-21 14:40 ` Chmouel Boudjnah
2001-05-21 14:29 ` Clint Adams
2001-05-21 15:37 ` Chmouel Boudjnah
2001-05-21 15:15 ` Clint Adams
2001-05-21 17:06 ` Oliver Kiddle
2001-05-21 17:12 ` Chmouel Boudjnah
2001-05-21 17:24 ` Andrej Borsenkow
2001-05-21 18:27 ` Chmouel Boudjnah
2001-05-21 15:50 ` Bart Schaefer [this message]
2001-05-21 18:17 ` Wayne Davison
2001-05-21 18:29 ` Andrej Borsenkow
2001-05-21 19:07 ` Bart Schaefer
2001-05-21 19:21 ` Chmouel Boudjnah
2001-05-21 10:54 ` [Cooker] " Chmouel Boudjnah
2001-05-20 18:26 ` Trond Eivind Glomsrød
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=1010521155045.ZM10521@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=chmouel@mandrakesoft.com \
--cc=cooker@linux-mandrake.com \
--cc=zsh-workers@sunsite.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).