From: "clemens fischer" <ino-qc@spotteswoode.de.eu.org>
To: "Borzenkov Andrey" <Andrey.Borzenkov@siemens.com>
Cc: "'Oliver Kiddle'" <okiddle@yahoo.co.uk>, zsh-users@sunsite.dk
Subject: Re: bash convert: new completion system skeleton?
Date: 24 Jan 2003 20:37:31 +0100 [thread overview]
Message-ID: <vg0ebapw.fsf@ID-23066.news.dfncis.de> (raw)
In-Reply-To: <6134254DE87BD411908B00A0C99B044F03A0B5FF@mowd019a.mow.siemens.ru> (Borzenkov Andrey's message of "Fri, 24 Jan 2003 14:19:04 +0300")
Borzenkov Andrey <Andrey.Borzenkov@siemens.com>:
>> I could easily write a function to allow zsh to use completions written
>> for bash:
this would get you into a hell of troubles you were leaving with the
invention of the new zsh-completion-system. think about special
cases popping up every place and all the work of keeping it!
> Or scan bash_profile/bashrc for complete -F and compdef all commands to use
> wrapper unless already defined. It would allow almost transparent change
> between bash and zsh. It could be added to compinstall then or even to
> compinit with style to turn it off/on.
>
> Would it be useful?
i don't think so. bash completers resemble the old completion style
with compctl much more.
>> Of course it is better to rewrite the functions properly to make
>> full use of zsh's greater power.
exactly. this is more a problem of documentation then programming,
because the facilities are already there. i just got lost in all the
stuff. the freebsd port maintainers put all the `_*' functions
containing zsh features at various levels into one single, flat
directory, so for me, who couldn't differentiate between widgets,
low- and high-level functions the interface layers were not clear.
but Borzenkov was nice enough to send me some pointers, so i think i
can take it from here. thanks, Borzenkov!
zsh needs more documentation with elaborate examples, that's all. i
know, it's the hardest part of it all ...
clemens
next prev parent reply other threads:[~2003-01-24 19:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 13:16 clemens fischer
2003-01-24 10:37 ` Peter Stephenson
2003-01-24 10:42 ` Borzenkov Andrey
2003-01-24 11:12 ` Oliver Kiddle
2003-01-24 11:19 ` Borzenkov Andrey
2003-01-24 19:37 ` clemens fischer [this message]
2003-01-24 21:19 ` John Buttery
2003-01-27 10:08 ` Oliver Kiddle
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=vg0ebapw.fsf@ID-23066.news.dfncis.de \
--to=ino-qc@spotteswoode.de.eu.org \
--cc=Andrey.Borzenkov@siemens.com \
--cc=okiddle@yahoo.co.uk \
--cc=zsh-users@sunsite.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).