From: teg@redhat.com (Trond Eivind Glomsrød)
To: Zefram <zefram@fysh.org>
Cc: Adam Spiers <adam@spiers.net>,
zsh workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: Re: PATCH: Re: adding a toplevel zsh.spec.in file
Date: 18 Jul 2000 14:22:26 -0400 [thread overview]
Message-ID: <xuyu2dnl2n1.fsf@hoser.devel.redhat.com> (raw)
In-Reply-To: Zefram's message of "Tue, 18 Jul 2000 02:56:04 +0100 (BST)"
Zefram <zefram@fysh.org> writes:
> Adam Spiers wrote:
> >In /etc/zshenv:
> >
> > export USER=`id -un`
> > export LOGNAME=$USER
> > export HOSTNAME=$HOST
> >
> > # this only on appropriate boxes of course
> > export MAIL=/var/spool/mail/$USER
>
> These, if they exist at all (which is OK if done right), should be in
> /etc/zprofile, and duplicated in /etc/profile. They should be set
> on *login*, not for every shell I start -- if I want to set MAIL to
> somewhere different, that setting should propagate to any subshells I run.
>
> > HISTSIZE=1000
> > HISTFILE=~/.zshhistory
> > SAVEHIST=1000
>
> No way. zsh has a perfectly well-established default behaviour
> w.r.t. history saving, and if I don't override it I should get zsh's
> default, not whatever some RPM builder thought might be nice.
>
> > export INPUTRC=/etc/inputrc
In Red Hat Linux, we do this:
if [ -z "$INPUTRC" -a ! -f "$HOME/.inputrc" ]; then
INPUTRC=/etc/inputrc
fi
The reason for this is to make bash 1.x handle 8 bit input - we don't
set anything else.
> My environment is my own.
Of course, and you're free to change it in your own files - but that
doesn't mean systems should be set up with sensible values (like
specifying NNTPSERVER, MAIL, QTDIR etc. etc).
> >Now here's a candidate for StartupFiles/RedHat/zshrc. Anything badly
> >wrong?
> ...
> ># Set up aliases
> >alias mv='nocorrect mv' # no spelling correction on mv
> >alias cp='nocorrect cp' # no spelling correction on cp
> >alias mkdir='nocorrect mkdir' # no spelling correction on mkdir
>
> Evil.
Agreed. Such changes should be in a user's own configuration files.
> >PS1='%n@%m %B%3~%b %# ' # default prompt
>
> Just don't. As before, you're overriding a perfectly reasonable
> default and imposing your arbitrary tastes on people.
If it makes sense, do it - it's just another default, a user can
override it. The default BASH prompt is "bash-2.04#", and changing
this to something more sensible is good (IMHO, of course - and if you
don't like it, pick your own).
> So here's my recomendation for zsh RPM builders: ship no /etc/zshrc,
> /etc/zshenv, /etc/zlogin or /etc/zlogout, and have /etc/zprofile
> be a symbolic link -> profile. (This still leaves a broken Red Hat
> /etc/profile, but that's outside the scope of a zsh package.)
It's not broken, it's just not designed to handle zsh - it's designed
to handle bash only. Fixing this (setting another default prompt for
zsh) should be simple if required.
--
Trond Eivind Glomsrød
Red Hat, Inc.
next prev parent reply other threads:[~2000-07-18 18:23 UTC|newest]
Thread overview: 27+ 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
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 [this message]
2000-07-18 19:57 ` Zefram
2000-07-18 20:07 ` Trond Eivind Glomsrød
2000-07-18 20:37 ` Zefram
2000-07-18 15:40 zefram
2000-07-18 16:37 ` Andrej Borsenkow
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=xuyu2dnl2n1.fsf@hoser.devel.redhat.com \
--to=teg@redhat.com \
--cc=adam@spiers.net \
--cc=zefram@fysh.org \
--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).