Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Mandrake 8.0 - compinit in /etc/zshrc
- X-seq: zsh-workers 14426
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: Chmouel Boudjnah <chmouel@xxxxxxxxxxxxxxxx>
- Subject: Re: Mandrake 8.0 - compinit in /etc/zshrc
- Date: Mon, 21 May 2001 12:07:00 -0700
- Cc: <cooker@xxxxxxxxxxxxxxxxxx>, Zsh Workers <zsh-workers@xxxxxxxxxx>
- In-reply-to: <Pine.LNX.4.33L2.0105211106540.1399-100000@xxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <Pine.LNX.4.33L2.0105211106540.1399-100000@xxxxxxxxxxxxxxx>
On May 21, 11:17am, Wayne Davison wrote:
> Subject: Re: Mandrake 8.0 - compinit in /etc/zshrc
> On 21 May 2001, Chmouel Boudjnah wrote:
> > and how do you do when you have to modify the skel file on upgrade ?
>
> Here's an alternate solution. See if you like this.
>
> For a package such as zsh, create a patch in the source rpm that adds
> an extra rc-file check that works like this: If the user's rc file is
> missing, we read the default rc file from /usr/lib/zsh (or similar).
It wouldn't be necessary to modify the source for that, would it? The
last line of /etc/zshrc would just need to be:
[[ -r ${ZDOTDIR:-$HOME}/.zshrc ]] || source /usr/lib/zsh/power_options
This is basically the same as my function-based suggestion except that
you never create the ~/.zshrc file for the user.
} The only
} downside I see in this is that the user needs to be made aware that when
} they create their own rc file, that they may wish to copy the default rc
} file and modify that rather than starting from scratch.
Making them aware of that is the reason for creating their .zshrc with some
kind of comment embedded in it. But it works passably either way.
--
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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author