From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
zsh-users@sunsite.auc.dk
Cc: Matthias Kopfermann <kopfermann@trio-hittfeld.de>
Subject: Re: (forw) --help able programs and completion]
Date: Mon, 26 Jun 2000 15:19:01 +0000 [thread overview]
Message-ID: <1000626151901.ZM25800@candle.brasslantern.com> (raw)
In-Reply-To: <200006261112.NAA19632@beta.informatik.hu-berlin.de>
On Jun 26, 1:12pm, Sven Wischnowsky wrote:
} Subject: Re: (forw) --help able programs and completion]
}
} > > We have a function to complete the options described by the `--help'
} > > output, it's called `_use_lo'
} > Hmm, a name that really does not explain anything, does it?
It stands for "use long options", because it used to be a wrapper for the
now-defunct _long_options completer (which was completely subsumed by
_arguments some while back).
} > So in order to use it one has to know it first :)
}
} Yes.
However, note that all it does is call _arguments, which is what 98% of
the completers for other commands also do. So most commands for which
there is a special completion already have the ability to complete based
on --help output: It's triggered by completing after `--'. Try, for
example
% tar --<TAB>
and watch the fun.
Which reminds me, Sven: There's still the bug where setting the `menu'
style to `select=N' for some number N is not working at all. Menu
selection never starts for me.
} The one who wrote it probably should have documented it
} somewhere.
}
} I /think/ it wasn't me this time.
This is very interesting.
The earliest mention of _use_lo in the zsh-workers archive is PWS saying
"What happened to _use_lo? I don't remember removing it." just before he
made the 3.1.6-test-1 release. That's the first time it shows up in my
home CVS repository, too. The ChangeLog-Release file doesn't mention it
at all until Sven started patching it (and the entire contents except for
the comment at the top have long been Sven's doing, even if he didn't
create the file originally).
Of course, the ChangeLog also doesn't make any mention of when _arguments
acquired the internals of _long_options.
--
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-06-26 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-26 11:12 Sven Wischnowsky
2000-06-26 15:19 ` Bart Schaefer [this message]
2000-06-26 15:34 ` Matt Armstrong
2000-06-26 16:03 ` Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
2000-06-27 11:08 Sven Wischnowsky
2000-06-27 14:36 ` Bart Schaefer
2000-06-27 14:46 ` Andrej Borsenkow
2000-06-26 11:08 Matthias Kopfermann
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=1000626151901.ZM25800@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=kopfermann@trio-hittfeld.de \
--cc=wischnow@informatik.hu-berlin.de \
--cc=zsh-users@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).