From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: compinit/compdef useful outside of completion?
Date: Tue, 29 Jun 1999 14:03:16 +0200 (MET DST) [thread overview]
Message-ID: <199906291203.OAA23049@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of Tue, 29 Jun 1999 15:47:25 +0400
Andrej Borsenkow wrote:
> Don't you think, that these can be used not only with completion widgets? I
> actually like the idea, when I just need to drop a file in defined place and it
> will automatically be used next time I start shell. No more .zshrc editing etc.
>
> What I mean, does it make sense to extend compinit/compdef to handle "normal"
> user defined widgets as well ('course, the names will probably be too misleading
> ...). E.g. 'compdef -w widget function' to define normal widget. You could even
> automatically bind it to key sequence with additional parameter ... say "-k
> ^Xn"?
> And start function with '#compdef -w <widget>'
I've been thinking about this, too. Some kind of autoauto-functions
with arguments describing the tags to expect and what to do with
them. Or some external configuration and then cal autoauto or
whatever. (Heck, haven't I mentioned that yet? I thought I had, but
maybe I've been only thinking too much about it.)
This is even more interesting if we once get into heavy widget-hacking.
What I'm currently thinking about is how we could generalise the
dumping code and integrate it with a generic autoauto function.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-06-29 12:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-29 12:03 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-06-29 11:47 Andrej Borsenkow
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=199906291203.OAA23049@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).