From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: expansion
Date: Wed, 14 Jun 2000 08:21:41 +0200 (MET DST) [thread overview]
Message-ID: <200006140621.IAA00961@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Tue, 13 Jun 2000 16:41:38 +0000
Bart Schaefer wrote:
> On Jun 13, 1:24pm, Sven Wischnowsky wrote:
> } Subject: PATCH: expansion
> }
> } Note that I've used the same default value in _expand as it has
> } elsewhere (`false'), which means that without further configuring,
> } this now behaves differently. Should we make it default to `true' in
> } _expand?
>
> If it now behaves by default more like the way the old expand-or-complete
> behaved, then I think we should leave it.
It is more like e-o-c. So this makes me wonder if the default for the
suffix style should be changed (currently its default is like the old
_expand, changing it would make it like e-o-c).
> Either that or the default
> should be different depending on whether _expand was used as a completer
> or called from _expand_word ... hrmm ...
I'm never too happy with adding differences between a completer and
the bindable command for it...
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-06-14 9:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-14 6:21 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-13 11:24 Sven Wischnowsky
2000-06-13 16:41 ` Bart Schaefer
2000-06-09 7:32 Sven Wischnowsky
2000-06-09 10:45 ` Oliver Kiddle
[not found] <0FVU001OT0DZC6@la-la.cambridgesiliconradio.com>
2000-06-08 16:50 ` Oliver Kiddle
2000-06-07 6:46 PATCH: expansion (was: Re: PATCH: Re: blah*[TAB] (difference between 3.1.6 and 3.1.9)) Sven Wischnowsky
2000-06-07 22:21 ` PATCH: expansion Wayne Davison
2000-06-08 10:03 ` Oliver Kiddle
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=200006140621.IAA00961@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--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).