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: Mon, 17 Jul 2000 19:07:28 +0100	[thread overview]
Message-ID: <20000717190728.A9091@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <1000717174853.ZM22633@candle.brasslantern.com>; from schaefer@candle.brasslantern.com on Mon, Jul 17, 2000 at 05:48:53PM +0000

Bart Schaefer (schaefer@candle.brasslantern.com) wrote:
> I agree that these don't do much harm, but this is bad:
> 
> }   HISTSIZE=1000
> }   HISTFILE=~/.zshhistory
> }   SAVEHIST=1000
> 
> Please don't mess with the shape of my history or the location of any of
> my dotfiles.

Why is this messing with your preferences?  It's only setting a
default which each user can override, surely?

> } Now here's a candidate for StartupFiles/RedHat/zshrc.  Anything badly
> } wrong?
> 
> Yes.  Don't screw with my fpath and don't autoload functions for me.

Again, I must be missing something because I don't see why you
describe this as messing with /your/ fpath when at that stage you (the
user) haven't made any changes to it.  You are still free to set it to
whatever you want, aren't you?  The only possible problem I can
envisage is that something gets autoloaded which you didn't want to
be, but if you didn't want it autoloaded, you won't be using it
anyway.  What am I missing?

> Your assumptions about where under my home directory there might be
> functions are wrong,

I wanted to err on the side of convenience.  If those directories
exist, the likelihood is that they contain stuff which the user will
want to use.  If they don't, they don't get included.  What's the
harm?

> and if your RPM is built correctly there shouldn't be anything
> useful in /usr/doc/zsh*/Functions -- the only things that could be there
> are leftovers from some 3.0.x-y RPM, which you don't want to pick up.

Yep, this is a remnant from old code.

> I won't call the aliases "badly" wrong, but I object to them anyway,

I'm curious now.  Why?

> and I'd just as soon not have all that crap in my prompt, thanks.

Just another default, surely?

I have a nasty feeling I've missed a key point here.


  reply	other threads:[~2000-07-17 18:07 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 [this message]
2000-07-17 21:05             ` Oliver Kiddle
2000-07-17 23:35               ` Adam Spiers
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=20000717190728.A9091@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).