Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Good, easy to use, upstream defaults for zsh (i.e. improving usability)
- X-seq: zsh-workers 21462
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: Good, easy to use, upstream defaults for zsh (i.e. improving usability)
- Date: Thu, 14 Jul 2005 15:06:08 +0000
- In-reply-to: <200507141203.j6EC3Ktf015537@xxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <ef5675f305071015374c036f2f@xxxxxxxxxxxxxx> <3060c2390507101559320eb09c@xxxxxxxxxxxxxx> <ef5675f305071016226f9d44ce@xxxxxxxxxxxxxx> <200507141203.j6EC3Ktf015537@xxxxxxxxxxxxxx>
On Jul 14, 1:03pm, Peter Stephenson wrote:
}
} Bart said most things, but I'm quite happy to consider innovative ideas
} as to how we can arrange for a useful default configuration without
} trashing the system's or the user's zsh initialisation scripts. This
} isn't an easy problem, and I don't think there's anyway of doing it
} without at least some connivance from system administrators and package
} maintainers.
Here's something that occurred to me:
During startup, if none of the ${ZDOTDIR:-$HOME}/.z* files are found,
zsh looks for (but does not complain if it does not find) a "new user"
module, e.g. zsh/newuser, and loads it.
(Or the module could be loaded unconditionally, and the test for whether
the .z* files exist could be part of the module bootup.)
We could provide a default implementation of zsh/newuser that looks
for files in /usr/share/zsh/$VERSION (or the equivalent configure-
time path) and either simply reads them, or copies them to the .z*
locations. Admins who don't want this could choose not to install
the module, or could provide their own rewrite.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author