From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Sven Wischnowsky" <wischnow@informatik.hu-berlin.de>,
<zsh-workers@sunsite.auc.dk>
Subject: RE: RFD: Zsh styles and OOP ...
Date: Tue, 15 Feb 2000 13:39:17 +0300 [thread overview]
Message-ID: <000701bf77a0$e8f0a160$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <200002151010.LAA12030@beta.informatik.hu-berlin.de>
> >
> > This is certainly interesting. Unfortunately it's going to
> make the whole
> > thing even more complicated, both for implementation and use.
> Furthermore,
> > we really need this to be right in 3.1.7 --- I would be against
> rewriting
> > the configuration for completion yet again.
>
> You are not alone here...
>
The only problem is, it will be more and more hard to change anything after
ZSH is released.
>
> I may also repeat my suggestion that we can put the context-finding
> code from _complete and _normal into a separate function. This could
> then be called at the very beginning (bindable commands,
> _main_complete). It would at least fill the context/command field of
> the context name.
It is not a question of missing context bits. The problem is, these bits are
completely meaningless in some cases. Unless we want to use different
completers for different commands, it does not help to know, what command is
being completed.
I just wish, that context names properly reflect there usage :-)
/andrej
next prev parent reply other threads:[~2000-02-15 10:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-15 10:10 Sven Wischnowsky
2000-02-15 10:39 ` Andrej Borsenkow [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-02-15 12:08 Sven Wischnowsky
2000-02-14 10:50 Andrej Borsenkow
2000-02-14 19:13 ` Peter Stephenson
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='000701bf77a0$e8f0a160$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--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).