zsh-workers
 help / color / mirror / code / Atom feed
From: Adam Spiers <adam@spiers.net>
To: zsh workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: Re: adding a toplevel zsh.spec.in file
Date: Tue, 18 Jul 2000 00:35:28 +0100	[thread overview]
Message-ID: <20000718003528.A11704@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <3973751E.2CFC476E@u.genie.co.uk>; from opk@u.genie.co.uk on Mon, Jul 17, 2000 at 10:05:34PM +0100

Oliver Kiddle (opk@u.genie.co.uk) wrote:
> 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,

The scripts I'm talking about are far far away from enabling bells and
whistles.  They just have a few things to smooth the edges of an
otherwise very raw installation.

[As an aside, I sometimes wonder why we don't make a
bells-and-whistles out of the box install of zsh much more easily
obtainable.  After all, the vast majority of people only use zsh for
its 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.

Or in the example startups, but commented out.  Remember, if we
provide a decent set of RedHat (say) startup scripts, it's likely that
within two years every recent RedHat box will have them installed, and
most people aren't going to be looking at the zsh web site when
they're editing them.

> Anything in the distribution is likely to be taken as something
> which is supposed to be installed in /etc.

Which is exactly what StartupFiles/RedHat/* would be, no?


  reply	other threads:[~2000-07-17 23:35 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-07 11:53 Adam Spiers
2000-07-07 12:45 ` Peter Stephenson
2000-07-07 16:15 ` Chmouel Boudjnah
2000-07-17 14:56   ` Adam Spiers
2000-07-07 17:18 ` Bart Schaefer
2000-07-07 17:44   ` Zefram
2000-07-07 18:18     ` Bart Schaefer
2000-07-17 15:09       ` Adam Spiers
2000-07-17 17:48         ` Bart Schaefer
2000-07-17 18:07           ` Adam Spiers
2000-07-17 21:05             ` Oliver Kiddle
2000-07-17 23:35               ` Adam Spiers [this message]
2000-07-18  2:32                 ` Trond Eivind Glomsrød
2000-07-18  6:01                 ` Bart Schaefer
2000-07-18  1:56         ` PATCH: " Zefram
2000-07-18  5:22           ` Bart Schaefer
2000-07-18  6:15             ` Wayne Davison
2000-07-18  8:31               ` How to distribute skeleton zshrc etc. (Re: PATCH: Re: adding a toplevel zsh.spec.in file) Bart Schaefer
2000-07-18 16:54             ` PATCH: Re: adding a toplevel zsh.spec.in file Trond Eivind Glomsrød
2000-07-18  6:25           ` Andrej Borsenkow
2000-07-18  9:42           ` Peter Stephenson
2000-07-18 18:22           ` Trond Eivind Glomsrød
2000-07-18 19:57             ` Zefram
2000-07-18 20:07               ` Trond Eivind Glomsrød
2000-07-18 20:37                 ` Zefram

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=20000718003528.A11704@thelonious.new.ox.ac.uk \
    --to=adam@spiers.net \
    --cc=zsh-workers@sunsite.auc.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).