From: Bart Schaefer <schaefer@tiny.zanshin.com>
To: zsh-workers@sunsite.auc.dk
Subject: Should _long_options be considered dangerous?
Date: Wed, 17 Mar 1999 23:04:04 -0800 (PST) [thread overview]
Message-ID: <14064.42340.65376.521996@localhost.localdomain> (raw)
I wonder if perhaps we shouldn't add some more warning text in
Completion/Base/_long_options (and maybe even in Completion/README)
noting that you shouldn't attempt to use _long_options from _normal
or any other "default" completion function.
Some (non-GNU) commands might actually do something unpleasant when
run with an unrecognized --help option. I can't think of an example
offhand, which is why the Subject is a question, but ...
next reply other threads:[~1999-03-18 7:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-18 7:04 Bart Schaefer [this message]
1999-03-18 8:04 Sven Wischnowsky
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=14064.42340.65376.521996@localhost.localdomain \
--to=schaefer@tiny.zanshin.com \
--cc=schaefer@brasslantern.com \
--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).