From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: _call (was: Re: PATCH: _diff (new), _prcs (upgrade))
Date: Thu, 3 Feb 2000 10:16:20 +0100 (MET) [thread overview]
Message-ID: <200002030916.KAA10368@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Alexandre Duret-Lutz's message of 02 Feb 2000 17:51:02 +0100
Alexandre Duret-Lutz wrote:
> Sven> The only problem is that -- in cases like the _diff -- the users would
> Sven> have to know what the command has to do, but as long as we keep tags
> Sven> and styles documented...
>
> Could there be a way to make the completion
> functions autodescribe themselve? (i.e.
> print styles and tags used by the function,
> as well as other info worth to know, in some
> standard way). Perhaps it can be made by
> using some special comments in the completions
> functions and having a simple shell
> function that take a command as argument,
> that find the completion function
> associated and format out these comments.
For the tags there is alread _complete_help, but, as I already said
some time ago (answering a question from Andrej, I think): we can't
really find out which styles are used by a function for a certain
context because they can be tested anywhere and anytime. Because of
that I was thinking about some comment-collecting function like what
you suggested. Finding the functions (and -files) that are used is
simple (_complete_help already does that). The problem is the amount
of work that has to be done to write the comments.
And if we do that we should first try to define a comment-format
containing everything we probably might want to find out about
completion functions and that can also be used to automatically
generate tables/lists for the manual/info.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-02-03 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-03 9:16 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-02-02 14:27 Sven Wischnowsky
2000-02-02 14:21 Sven Wischnowsky
2000-02-02 16:51 ` Alexandre Duret-Lutz
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=200002030916.KAA10368@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).