Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: adding a toplevel zsh.spec.in file
- X-seq: zsh-workers 12285
- From: Oliver Kiddle <opk@xxxxxxxxxxxxx>
- To: zsh workers mailing list <zsh-workers@xxxxxxxxxxxxxx>
- Subject: Re: adding a toplevel zsh.spec.in file
- Date: Mon, 17 Jul 2000 22:05:34 +0100
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <E13AcAZ-0004bN-00@xxxxxxxxxxxxxxxxxx> <1000707181834.ZM1473@xxxxxxxxxxxxxxxxxxxxxxx> <20000717160933.B6739@xxxxxxxxxxxxxxxxxxxxxxx> <1000717174853.ZM22633@xxxxxxxxxxxxxxxxxxxxxxx> <20000717190728.A9091@xxxxxxxxxxxxxxxxxxxxxxx>
- Sender: opk
I very much agree with Bart on these points.
If we are going to have default /etc/z* files in a generated rpm package
they should be as minimal as possible. We should stress the point to
people installing zsh that they should only put things in global setup
files that really should be in them. My definition of that is only
things which are necessary for the specifics of the local setup so only
adding a few things to the PATH and setting any variables necessary for
programs to run.
Adam Spiers wrote:
> > } HISTSIZE=1000
> > } HISTFILE=~/.zshhistory
> Why is this messing with your preferences? It's only setting a
> default which each user can override, surely?
Maybe a user can override it but it isn't necessarily obvious whether
the significant value for these variables is the first or last value
they get. I never trust these things until I've checked them out. I also
sometimes like to know that I have a clean zsh when I run it as a
different user or whatever.
If we want to provide examples of clever zsh startup files which enable
all the bells and whistles, I think it is much better to put them on the
web page where they can clearly be labeled as what they are. Anything in
the distribution is likely to be taken as something which is supposed to
be installed in /etc.
Oliver
Messages sorted by:
Reverse Date,
Date,
Thread,
Author