From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: completion in vared
Date: Mon, 3 May 1999 10:14:29 +0200 (MET DST) [thread overview]
Message-ID: <199905030814.KAA28717@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Fri, 30 Apr 1999 11:40:57 -0700
Bart Schaefer wrote:
> No, I'm mostly thinking of the compctl options that have poor mnemonics,
> and particularly of -J and -V (which are begging for a bracketed-looking
> syntax).
Are you meaning something like: start-group, ..., end-group?
In the beginning we had -[JV] set the group permanently (until the
next -[JV]) which was nearer to this but then I decided against it
because in more complex compctl's (or now: completion functions) you
would always have to use it to make sure that you know which group you
are using. And with such a pair you would have to remember to reset
it. Also, to make this usable we would have to implement a kind of
stack, so that the end-group resets it to the previous group again.
> There is some advantage to having the options of the new commands be the
> same as those of compctl, but I'm not sure if it's enough to outweigh the
> opportunity to clean it up a bit.
Right, we might think about this. For me, the most important advantage
of the current implementation is that it can easily share all the
parsing code with compctl. I might be convinced to change it, though.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-05-03 8:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-03 8:14 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-04-30 7:07 Sven Wischnowsky
1999-04-30 18:40 ` Bart Schaefer
1999-04-29 9:05 Sven Wischnowsky
1999-04-29 16:42 ` Bart Schaefer
1999-04-28 15:00 Peter Stephenson
1999-04-28 17:59 ` 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=199905030814.KAA28717@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).