From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@math.gatech.edu
Subject: Re: Latest patched development version
Date: Mon, 11 Jan 1999 11:05:39 +0100 (MET) [thread overview]
Message-ID: <199901111005.LAA20539@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Sun, 10 Jan 1999 18:38:28 -0800
Bart Schaefer wrote:
>
> A long time ago, in a year far far away, Sven Wischnowsky wrote:
> } Bruce Stephens wrote:
> } > Bruce Stephens <b.stephens@isode.com> writes:
> } >
> } > > Completion seems to have vanished, but I just tried with zsh -f, and
> } > > it works again, so that's presumably just something that's changed
> } > > in the compctl syntax that's not being reported as an error.
> } >
> } > I've found it. It was this example completion:
> } >
> } > compctl -Tx 's[/home/] C[0,^/home/*/*]' -S '/' \
> } > -s '$(niscat auto_home.org_dir | \
> } > awk '\''/export\/[a-zA-Z]*$/ {print $NF}'\'' FS=/)'
> }
> } Peter's version contains my patch for completion continuing. With this
> } we almost ever need a `-tc' in the `-T' completion.
> }
> } (I said that trouble would come of that...)
>
> Is there any reason that -tc simply can't be implicit? That is, why not
> always continue with the next suitable completion, leaving -t+ -t- and -tx
> to change what "next suitable" means? And then perhaps throw in something
> like -tn to mean "no, DON'T continue."
>
> Seems to me it's more often the case that you want to go on trying other
> possible completions rather than giving up. The default should be what
> the most common case is.
I wanted to leave the previous behavior unchanged as much as
possible. The `-T' is the only case where multiple compctl's were
tested in all other cases making -t<whatever> implicit would make
things differ from the way it was before my patches.
So we could make -tc implicit for -T (at least the `global' -tc,
before any -x). That would make things behave like they always did but
I didn't like to add special cases at that time.
Anyway before I change anything I would like to hear a bit more what
people would like to have, ok?
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-01-11 10:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-11 10:05 Sven Wischnowsky [this message]
1999-01-12 17:34 ` Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
1999-01-21 9:42 Sven Wischnowsky
1998-12-15 14:57 Sven Wischnowsky
1999-01-11 2:38 ` Bart Schaefer
1998-12-15 11:59 Sven Wischnowsky
1998-12-15 13:05 ` Peter Stephenson
1998-12-15 14:03 ` Bruce Stephens
1998-12-15 14:44 ` Bruce Stephens
1998-12-14 13:57 Peter Stephenson
1998-12-14 17:05 ` Bruce Stephens
1998-12-14 17:27 ` Peter Stephenson
1998-12-14 17:31 ` Bruce Stephens
1998-12-14 18:54 ` Phil Pennock
1998-12-14 20:13 ` 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=199901111005.LAA20539@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--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).