zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <opk@u.genie.co.uk>
To: zsh-workers@sunsite.dk
Cc: cooker@linux-mandrake.com
Subject: Re: Mandrake 8.0 - compinit in /etc/zshrc
Date: Mon, 21 May 2001 18:06:54 +0100	[thread overview]
Message-ID: <3B094B2E.8BA2035@u.genie.co.uk> (raw)
In-Reply-To: <20010521111551.A14676@dman.com>

Bart Schaefer wrote:

> One possibility might be not to put the code directly into the skel file.
> Put it in, say, /etc/zsh.d/compinit.

This is much more sensible. Trying to modify existing user's .zshrc
files would be fraught with problems and bound to irritate some users.

Clint Adams wrote:

> You could conceivably check from the global startup scripts, or
> from the initial /etc/skel/.z*, whether or not a dotfile upgrade
> is in order.

What you could do, from the global .zlogin, is have something like:
if [[ /etc/skel/.zshrc -nt ~/.zshrc ]]; then
  echo Warning: skeleton .zshrc has changed
  touch ~/.zshrc  # display above message only once
fi

That way, old users would be alerted to the change and could update
their own .zshrc if they wanted.

Maybe we should allow zsh to be given some shell code at compile time
which would then be run at startup along with all the dot files. There'd
need to be a way to disable it (similar to the norcs option) and we'd
need to work out when it would fit in with the order of everything else.
It'd be ideal for compinit and any future zsh features which might be
done in shell code.

Oliver

_____________________________________________________________________
This message has been checked for all known viruses by the 
MessageLabs Virus Scanning Service. For further information visit
http://www.messagelabs.com/stats.asp


  reply	other threads:[~2001-05-21 17:07 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 [this message]
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
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=3B094B2E.8BA2035@u.genie.co.uk \
    --to=opk@u.genie.co.uk \
    --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).