From: "Stefan Monnier" <monnier+lists/zsh/users/news/@tequila.cs.yale.edu>
To: zsh-users@sunsite.auc.dk
Subject: Re: Call for opinions on a couple of prospective zsh patches
Date: 06 Jun 1999 12:50:57 -0400 [thread overview]
Message-ID: <5lr9np8e8e.fsf@tequila.cs.yale.edu> (raw)
In-Reply-To: <990606065150.ZM9165@candle.brasslantern.com>
>>>>> "Bart" == Bart Schaefer <schaefer@candle.brasslantern.com> writes:
> * Completion using "dynamic abbreviations" after the manner of the emacs
[...]
> * Partial word motions in the face of mixed case, i.e. move the cursor to
[...]
> * Support for the LS_COLORS environment string, to colorize file names in
I think adding anything to 3.0 is a mistake. We should instead hurry to
get 3.2 out the door. 3.1.x has too many neat features that most people don't
get to use since RedHat and friends only come with 3.0.5.
Adding any of the three to 3.1 makes sense, but to 3.0 ?
I really wish the next 3.1.x were called 3.2.0.
Stefan
PS: GNU ls's LS_COLORS code is brain dead: if you want to include it at least
try to fix it so that its auto-detection of color capability is a bit less
pathetically optimistic (trying to colorize the output when TERM=dumb
is ...well... dumb!)
next prev parent reply other threads:[~1999-06-06 16:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-06 6:51 Bart Schaefer
1999-06-06 13:36 ` Adam Spiers
1999-06-06 16:20 ` Bart Schaefer
1999-06-06 14:13 ` Peter Stephenson
1999-06-06 16:40 ` Bart Schaefer
1999-06-09 16:34 ` WORDCHARS (Re: Call for opinions on a couple of prospective zsh patches) Bart Schaefer
1999-06-10 0:51 ` Stefan Monnier
1999-06-10 8:15 ` WORDCHARS, etc Peter Stephenson
1999-06-06 16:50 ` Stefan Monnier [this message]
1999-06-06 17:13 ` Call for opinions on a couple of prospective zsh patches Adam Spiers
1999-06-06 17:25 ` Bart Schaefer
1999-06-06 18:41 ` Stefan Monnier
1999-06-07 1:22 ` 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=5lr9np8e8e.fsf@tequila.cs.yale.edu \
--to=monnier+lists/zsh/users/news/@tequila.cs.yale.edu \
--cc=zsh-users@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).