From: Tanaka Akira <akr@jaist.ac.jp>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Completion/Cvs/
Date: 01 Sep 1999 19:35:17 +0900 [thread overview]
Message-ID: <rsqhflevs0q.fsf@crane.jaist.ac.jp> (raw)
In-Reply-To: Sven Wischnowsky's message of "Wed, 1 Sep 1999 11:25:47 +0200 (MET DST)"
In article <199909010925.LAA32701@beta.informatik.hu-berlin.de>,
Sven Wischnowsky <wischnow@informatik.hu-berlin.de> writes:
> In this example I think I would like to have it complete `vi' if the
> cursor is directly after the `-e' (same word), because the `*::...'
> should only take affect on whole words, i.e. in this case the word
> after the `-e...'.
Why? Since a first non-option argument is the `a', I think the
`*::...' should take affect the `-e...' after the `a'.
I want to stop completion by _arguments until first non-option
argument --- the `a'. So In the example, I want the behaviour that
there should be no completion after the `a'.
> With that, this is just a special case of a more general problem with
> completion after a `-e+:...' option. Currently we use the description
> for the first option-argument to complete the next word after the `-e'
> only if there really is nothing after the `-e' in the same word (so
> that `foo -e <TAB>' completes the option-argument and `foo -ebar <TAB>'
> completes normal arguments). But what if the empty string is a valid
> option-argument? I think `-e+::...' should give us that (that's what
> the patch below does).
I think this is another issue.
Even if the empty string is a valid option-argument, getopt does not
take the option-argument from the same word because getopt never
knows it. In general, it is impossible to parse command line with the
rule that enable the empty string option-argument just after (without
white space) the option-argument word. So I think it is useless.
--
Tanaka Akira
next prev parent reply other threads:[~1999-09-01 10:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-01 9:25 Sven Wischnowsky
1999-09-01 10:35 ` Tanaka Akira [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-09-01 12:23 Sven Wischnowsky
1999-09-01 11:03 Sven Wischnowsky
1999-09-01 12:01 ` Tanaka Akira
1999-08-31 15:03 Tanaka Akira
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=rsqhflevs0q.fsf@crane.jaist.ac.jp \
--to=akr@jaist.ac.jp \
--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).