From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
zsh-workers@sunsite.auc.dk
Subject: Re: _arguments parsing of --help output
Date: Tue, 25 Jul 2000 15:05:26 +0000 [thread overview]
Message-ID: <1000725150527.ZM19968@candle.brasslantern.com> (raw)
In-Reply-To: <200007240852.KAA05409@beta.informatik.hu-berlin.de>
On Jul 24, 10:52am, Sven Wischnowsky wrote:
} Subject: Re: _arguments parsing of --help output
}
} Bart Schaefer wrote:
}
} > Many GNU commands include short options in the --help output as well
} > [...]
} > Is there a reason that we don't attempt to complete the short forms?
}
} _arguments '-e:ea:(1 2)' -e -b -p
}
} This will make `foo -e <TAB>' complete `1' and `2' but `foo -' lists
} both (with auto-descriptions).
I don't understand here what you mean by "`foo -' lists both".
} The code in _arguments takes care that the user-supplied specs are
} preferred over the automatically derived ones, though.
Using the 3.1.9-dev-3 version of _arguments, I tried all of:
_tst() { _arguments '--e:ea:(1 2)' -- } # Case 1
_tst() { _arguments -- '--e:ea:(1 2)' } # Case 2
_tst() { _arguments -- '*--e:ea:(1 2)' } # Case 3
In combination with:
tst() { print -l - --e --b --p }
compdef _tst tst
Case 1: Completion after `tst' lists --e --b --p and completion after
`tst --e' lists 1 2.
Case 2: Completion after `tst' lists --e --b --p and completion after
`tst --e' completes `--' and then lists --b and --p; 1 or 2 are never
completed.
Case 3: Exactly like Case 2.
So case 1 behaves as I expected, and case 3 appears to be broken. (I
also tried '*e:ea:(1 2)' and a few other patterns.) I'm not sure what
I should be expecting from case 2.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2000-07-25 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-24 8:52 Sven Wischnowsky
2000-07-25 15:05 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-21 22:22 Bart Schaefer
2000-07-21 23:10 ` 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=1000725150527.ZM19968@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=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).