From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@math.gatech.edu
Subject: Re: completion behaviour (was: zsh-workers: zsh-3.1.5 released)
Date: Mon, 2 Nov 1998 14:48:10 +0100 (MET) [thread overview]
Message-ID: <199811021348.OAA22695@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Zefram"'s message of Mon, 2 Nov 1998 12:31:43 +0000 (GMT)
Zefram wrote:
> ...
>
> >Partly agreed (see above), but I would still like to give the user
> >some more support. Think of `r[-exec,;]'. The user would have to do the
> >matching and before (s)he can produce matches (s)he would have to tell
> >the completion code which command words should not be used. This can
> >get a bit nasty.
>
> What you need there is for the user-defined completion function, after
> recognising the "-exec", to recursively invoke the completion mechanism
> on the restricted range of words. As long as completion can be invoked
> recursively, there's no need for more specific support for this type
> of construct. (Consider also how to properly handle completion of the
> word after "sh -c".)
>
Let's clear this once and for all. Currently the testing code produces
two types of information: the length of an ignored prefix and a
possible range restriction in the command words. Without special
support, the user would have to do the test and then manually notify
the completion code of the restrictions to use (the prefix stuff for
almost all completions and the range restriction for `-l' which is
your example). In some cases this is trivial (e.g. for `S[-]'), in
some cases it is not that easy (e.g. `n[-1,/]' or `r[-exec,;]').
Personally I don't care if we would have to manually notify the
completion code, but I guess some users would like to have an easier
way. On the other hand, we could put examples for the most obvious
things in the manual.
Maybe I'll write an updated version of my suggestion in the next days.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next prev reply other threads:[~1998-11-02 13:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-02 10:36 Sven Wischnowsky
1998-11-02 10:39 ` Peter Stephenson
1998-11-02 11:29 ` Zefram
1998-11-02 12:00 ` Sven Wischnowsky
1998-11-02 12:31 ` Zefram
1998-11-02 13:48 ` Sven Wischnowsky [this message]
1998-11-03 15:58 ` new completion behaviour version 2 Sven Wischnowsky
1998-11-03 17:15 ` Bart Schaefer
1998-11-06 19:02 ` 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=199811021348.OAA22695@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).