Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
A scheme to manage several ZSH config file collections?
- X-seq: zsh-users 13054
- From: "Richard Hartmann" <richih.mailinglist@xxxxxxxxx>
- To: "Zsh users list" <zsh-users@xxxxxxxxxx>, grml@xxxxxx
- Subject: A scheme to manage several ZSH config file collections?
- Date: Thu, 24 Jul 2008 13:48:43 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=Ri6T22E44gV7XqQbVxOZlzmQhYNF/NXHT0poaccD75E=; b=kFgafPiaC8VzzFxE8gIG3O6A+BXFgmI1VOl/DGecVewOkfx7/Lpx0DySPqy3y17tiS EwdObQ+uv0Vf87Bq89FmUph9lkY5QFQ/QV9jT3PSCHCnct4khZmwdBJlbOw/Rm4CL+Tg MqRQed7roGw04yX4rq7s2nqpMwA6/OZwY5YMg=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=eVg9tDIQcvu3JMDyWq6lMF4k/T35Q21lWnZnvCQBlgq2O3u1qDYf/OvzLarPA+OEPP 5N4sTX9WW1/b3fTlyLImOs6zCmgtpGyp3pJeSqU/dy9PEVLToj+l0V7JDYCi789pHsfw AcnrNoq1iqB5OZEeDR7zIlxvQd/8s0WCyrpgE=
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
Hi all,
some of you might be aware of grml, a live boot CD which uses ZSH as its
default shell. I suggested integrating several different zshrc files
along with whatever other files they need and offer the user a selection
of said configuration files.
Now, we are wondering if there is a clean and maintainable way to do
this. I have had a few ideas in this direction and would like to discuss
those here. New suggestions are more than welcome as well, of course.
Ideally, the same versions should be usable on the machines of whoever
maintains those files, so that changes can be merged back and forth
easily, which will allow more people to participate.
1) Make ZSH load the RC files from different paths (/etc/zsh/config1 ..)
Pro: Almost drop-in, minimal work necessary
Cleanly seperated
Different ttys might run with different RC files
Con: Needs modification to fpath etc
Shells can not be allowed to start prior to rc file selection
2) Use symlinks
Pro: Fast to set up
Con: All shells are forced to use the same RC files
Shells can not be allowed to start prior to rc file selection
Ugly & hackish
3) Use $ZSHRC_PREFIX or some similar variable
Pro: Drop-in solution once you change your RC files for the first
time
Cleanly seperated
Different ttys might run with different RC files
Con: Shells can not be allowed to start prior to rc file selection
Needs a way for ZSH to be started with a variable set before it
is invoked
Are there any other options? Pros or Cons I overlooked? Anything else?
The main thing I worry about is to make the shells wait for their RC
files in a robust & fail-safe way?
Personally, I lean towards solution 3, but I am not hell-bent onto using
it.
Thanks,
Richard
PS: Yes, in a second step, this system could be expanded for VIM
etc, as well.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author