From: "Bart Schaefer" <schaefer@brasslantern.com>
To: schizo@debian.org (Clint Adams), zsh-workers@math.gatech.edu
Subject: Re: histchars
Date: Sat, 29 Nov 1997 10:09:27 -0800 [thread overview]
Message-ID: <971129100927.ZM4522@candle.brasslantern.com> (raw)
In-Reply-To: <199711291555.KAA24555@ertugl.prospect.apt>
On Nov 29, 10:53am, Clint Adams wrote:
} Subject: Re: histchars
}
} > Hm. No offense, but ... do you guys always change anything that anybody
} > submits a bug report for?
}
} No. Do you disagree with the decision?
You yourself said you didn't know why it was necessary. The ChangeLog file
has these two entries from the same date:
Wed Jul 31 19:10:04 1996 Zoltan Hidvegi <hzoli@cs.elte.hu>
* Src/version.h: zsh-3.0-pre5 released
* Src/hashtable.h, Src/params.c, Src/zsh.h: {E,}{U,G}ID, USERNAME,
histchars, HISTCHARS, IFS are not imported
Since those variables were imported prior to 3.0, and that was deliberately
changed a year and a half ago, and nobody's complained to zsh-workers about
it in all that time, I tend to think that it ought to be left alone -- at
least until you know why it could be considered a bug. (Perhaps for bash
or ksh behavior equivalence?)
I'd actually prefer it if *fewer* variables, rather than more, were imported
when shells start up. It was fine when there were essentially two shells (sh
and csh) that shared no special variables; but now there are a dozen or more
sharing the same namespace. For example, there are about three shells with
incompatible formats for PS1; it's annoying when zsh imports bash's prompt.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1997-11-29 18:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-28 17:55 histchars Clint Adams
1997-11-28 19:01 ` histchars Bart Schaefer
1997-11-28 19:34 ` histchars Clint Adams
1997-11-28 22:51 ` histchars Bart Schaefer
1997-11-29 15:53 ` histchars Clint Adams
1997-11-29 18:09 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-05-23 17:50 HISTCHARS Barton E. Schaefer
1996-05-23 18:32 ` HISTCHARS Zoltan Hidvegi
1996-05-23 18:48 ` HISTCHARS Richard Coleman
1996-05-23 19:11 ` HISTCHARS Zoltan Hidvegi
1996-05-23 19:20 ` HISTCHARS Richard Coleman
1996-05-23 19:17 ` HISTCHARS Barton E. Schaefer
1996-05-23 19:36 ` HISTCHARS Zoltan Hidvegi
1996-05-23 19:43 ` HISTCHARS Barton E. Schaefer
1996-05-23 19:51 ` HISTCHARS Zoltan Hidvegi
1996-05-23 20:14 ` HISTCHARS Vinnie Shelton
1996-05-23 20:40 ` HISTCHARS Barton E. Schaefer
1996-05-23 21:00 ` HISTCHARS Zoltan Hidvegi
1996-05-24 17:51 ` HISTCHARS Bart Schaefer
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=971129100927.ZM4522@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=schizo@debian.org \
--cc=zsh-workers@math.gatech.edu \
/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).