From: "Zefram" <zefram@tao.co.uk>
To: wischnow@informatik.hu-berlin.de (Sven Wischnowsky)
Cc: zsh-workers@math.gatech.edu
Subject: Re: completion behaviour (was: zsh-workers: zsh-3.1.5 released)
Date: Mon, 2 Nov 1998 12:31:43 +0000 (GMT) [thread overview]
Message-ID: <199811021231.MAA12204@diamond.tao.co.uk> (raw)
In-Reply-To: <199811021200.NAA22140@beta.informatik.hu-berlin.de> from "Sven Wischnowsky" at Nov 2, 98 01:00:28 pm
Sven Wischnowsky wrote:
>So, if we are expecting to implement associative arrays with some
>really powerful mechanisms (think about the pattern matching stuff
>completion will/should support),
*double take*
Hmm, I didn't consider the pattern matching aspect when I suggested using
associative arrays. But since the existing hashtable code provides an
interface for pattern matching lookups, it shouldn't be difficult to
provide a user interface.
>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".)
-zefram
next prev parent reply other threads:[~1998-11-02 12:40 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 [this message]
1998-11-02 13:48 ` Sven Wischnowsky
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=199811021231.MAA12204@diamond.tao.co.uk \
--to=zefram@tao.co.uk \
--cc=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).