From: Bruce Stephens <b.stephens@isode.com>
To: zsh-workers@math.gatech.edu
Subject: Re: up-line-or-search still 'fixed'!
Date: 09 Jun 1998 16:50:39 +0100 [thread overview]
Message-ID: <vbu35utvzk.fsf@snake.isode.com> (raw)
In-Reply-To: "Bart Schaefer"'s message of "Tue, 9 Jun 1998 08:22:37 -0700"
"Bart Schaefer" <schaefer@brasslantern.com> writes:
> If this were the IETF (which thank goodness it isn't, but) we'd take
> a straw poll at this point. So far I'm "hearing" a lot of protest
> about this change from actual users of the shell and support only
> from those interested in internal architecture. Are we writing
> usable software or carrying on an academic excercise?
The former, but people are also aiming for internal beauty and
simplicity, I think. (Well, maybe it's more "practical
maintainability" than "simplicity".)
Maybe somebody could summarise the specific question? I've not
noticed any particular change recently: the last change that irritated
me a bit was the */ becoming *(/), which I understand was necessary,
but I used */ quite a bit.
Maybe if the interface that's changed was described concisely,
together with the reasons for changing it, then it would be obvious to
people that it was worth keeping, or some workaround would become
clearer?
next prev parent reply other threads:[~1998-06-09 15:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aheading@jpmorgan.com>
1998-02-09 13:23 ` Zle bug Wez Furlong
1998-04-28 12:34 ` up-line-or-search still 'fixed'! Anthony Heading
1998-04-28 13:21 ` Andy Wick
1998-04-28 13:33 ` Anthony Heading
1998-04-28 14:08 ` Andrew Main
1998-06-09 13:13 ` Anthony Heading
1998-06-09 15:22 ` Bart Schaefer
1998-06-09 15:50 ` Bruce Stephens [this message]
1998-06-09 18:42 ` Bart Schaefer
1998-06-10 10:14 ` Bruce Stephens
1998-06-10 10:31 ` Zefram
1998-06-10 11:57 ` Bruce Stephens
1998-06-10 17:13 ` Bart Schaefer
1998-06-10 5:18 ` message numbers in mla Geoff Wing
1998-06-22 11:16 ` Geoff Wing
1998-06-22 16:17 ` Bart Schaefer
1998-06-22 17:38 ` Richard Coleman
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=vbu35utvzk.fsf@snake.isode.com \
--to=b.stephens@isode.com \
--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).