From: Adam Spiers <adam@thelonious.new.ox.ac.uk>
To: Zsh hackers list <zsh-workers@sunsite.auc.dk>
Subject: Re: PATCH: completion for perldoc
Date: Tue, 7 Sep 1999 10:18:58 +0100 [thread overview]
Message-ID: <19990907101858.B7292@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <199909070857.KAA407243@hydra.ifh.de>; from Peter Stephenson on Tue, Sep 07, 1999 at 10:57:22AM +0200
Peter Stephenson (pws@ifh.de) wrote:
> Adam Spiers wrote:
> > > _perldoc {
> > > ...
> >
> > I forgot to say: this kills zsh :-(
>
> There's no () after _perldoc, so it thinks it's a function call, not a
> definition. You just generate hundreds of recursive calls to _perldoc
> until the machine gets board of having enough space on the stack, or
> something.
Yes, I'm ashamed to say this was indeed the problem, and as usually
happens, I only realised it after I'd posted.
> Also, since it's assumed in the completion functions that KSH_AUTOLOAD
> isn't set, you need to have as the last line `_perldoc "$@"' to call
> the function you've just defined.
Ah! So /that's/ why I was having to press TAB twice. Thanks.
> The may be a bug here. Has anyone the slightest idea why `_perldoc {'
> is accepted as a complete command line with the argument "{"?
Nope. I've been bitten by that more than just this once though; I
always forget the () ...
next prev parent reply other threads:[~1999-09-07 9:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-06 11:37 Sven Wischnowsky
1999-09-06 18:18 ` Adam Spiers
1999-09-06 18:21 ` Adam Spiers
1999-09-07 8:57 ` Peter Stephenson
1999-09-07 9:18 ` Adam Spiers [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-09-07 9:02 Sven Wischnowsky
1999-09-07 8:59 Sven Wischnowsky
1999-09-07 8:32 Sven Wischnowsky
1999-09-07 9:49 ` Adam Spiers
1999-09-06 9:28 Sven Wischnowsky
1999-09-06 10:07 ` Adam Spiers
1999-09-05 21:38 Adam Spiers
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=19990907101858.B7292@thelonious.new.ox.ac.uk \
--to=adam@thelonious.new.ox.ac.uk \
--cc=adam@spiers.net \
--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).