From: DervishD <raul@pleyades.net>
To: Oliver Kiddle <okiddle@yahoo.co.uk>
Cc: Zsh <zsh-workers@sunsite.dk>
Subject: Re: Tags in function files
Date: Wed, 17 Sep 2003 10:37:52 +0200 [thread overview]
Message-ID: <20030917083752.GC4415@DervishD> (raw)
In-Reply-To: <18188.1063784897@gmcs3.local>
Hi Oliver :)
* Oliver Kiddle <okiddle@yahoo.co.uk> dixit:
> > and #autoload), are hardcoded in Zsh or is the new completion system
> > who parses it? I mean, can I use those tags in my shell scripts
> > without using the new completion system?
> It is the compinit shell function which parses them. So it is just the
> new completion system and not anything hardcoded into zsh.
OK, thanks :) BTW, the special parameters as 'words' and the
like, are too created and initialized by compinit (I mean, the new
completion system...)? $words doesn't seem to work, so I'm thinking
about using 'BUFFER' for command line parsing in order to call one of
the completion functions I need. Like _main_complete, but lots
simpler.
> You can use them in your own shell scripts if you really want. You might
> regret it if you start using the new completion system later though so
> it might be wiser to use a different word in your tags.
I take note, thanks :))) Anyway I was asking just for avoiding
explicit calls to 'compdef', but I noticed that compdef is just a
function defined by compinit!, so I cannot use it. No problem anyway.
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/
next prev parent reply other threads:[~2003-09-17 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-16 20:35 DervishD
2003-09-17 7:48 ` Oliver Kiddle
2003-09-17 8:37 ` DervishD [this message]
2003-09-17 16:30 ` Bart Schaefer
2003-09-17 19:37 ` DervishD
2003-09-18 3:44 ` Bart Schaefer
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=20030917083752.GC4415@DervishD \
--to=raul@pleyades.net \
--cc=okiddle@yahoo.co.uk \
--cc=zsh-workers@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).