zsh-workers
 help / color / mirror / code / Atom feed
From: Zefram <zefram@fysh.org>
To: Trond Eivind=?iso-8859-1?q?_Glomsr=F8d?= <teg@redhat.com>
Cc: Zefram <zefram@fysh.org>,
	 zsh workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: Re: PATCH: Re: adding a toplevel zsh.spec.in file
Date: Tue, 18 Jul 2000 21:37:59 +0100 (BST)	[thread overview]
Message-ID: <E13Ee7s-0005sy-00@crucigera.fysh.org> (raw)
In-Reply-To: <xuyzonfjj6v.fsf@hoser.devel.redhat.com> from =?us-ascii?Q?Trond_Eivind=3D=3Fiso=2D8859=2D1=3Fq=3F=5FGlomsr?= =?us-ascii?Q?=3DF8d=3F=3D?= at "Jul 18, 2000 04:07:52 pm"

Trond Eivind=?iso-8859-1?q?_Glomsr=F8d?= wrote:
>The default value sucks (IMHO) - the alternative is patching the
>source, which would be much more confusing. The solution for zsh is
>simple - just set something in your .zshrc.
> 
>HISTSIZE isn't too bad (you can override it) and /etc/inputrc is
>necesarry to make bash 1.4x work with non-ASCII characters.

Setting the prompt, INPUTRC and so on by default without stepping
on users' toes is easy -- just set them in /etc/skel/.{ba,z}shrc.
There's no tradeoff required between default functionality and keeping
out of the way, there's no fine line to walk, /etc/skel lets you provide
arbitrarily clever functionality to users that don't attempt to configure
their shells at all while simultaneously leaving the shells' own standard
default settings completely unaffected and available to anyone that
wants to write their own dotfiles.

Given the availability of such a mechanism, any /etc/profile that fiddles
with the configuration of an interactive shell can only be regarded as
broken.  The argument about providing new functionality to users with
old dotfiles just doesn't hold water, especially when one is creating
a package to be used when setting up a new system, where there are no
existing users to be concerned about.

-zefram


  reply	other threads:[~2000-07-18 20:37 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
2000-07-18 19:57             ` Zefram
2000-07-18 20:07               ` Trond Eivind Glomsrød
2000-07-18 20:37                 ` Zefram [this message]
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=E13Ee7s-0005sy-00@crucigera.fysh.org \
    --to=zefram@fysh.org \
    --cc=teg@redhat.com \
    --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).