From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "ZSH Workers Mailing List" <zsh-workers@sunsite.dk>
Subject: Re: Debugging of dynamocally defined functions
Date: Sat, 7 Jul 2001 23:30:10 +0000 [thread overview]
Message-ID: <1010707233010.ZM16910@candle.brasslantern.com> (raw)
In-Reply-To: <000001c10514$04fa4580$21c9ca95@mow.siemens.ru>
On Jul 5, 9:33am, Andrej Borsenkow wrote:
} Subject: Debugging of dynamocally defined functions
}
} Honestly speaking, I never liked it (function defining other functions that
} is); why not simply have them autoloaded is beyond me.
In the case of compdef I agree with you -- it's complicated enough that it
should have an entry in the documentation (separate from the `#comdpef'
entries, which are deceptively similar but use slightly different syntax).
In other cases functions defining functions is quite appropriate; consider
the `compadd' front-end that's defined in _approximate or _complete_help.
Not only would it be a waste to put it in a separate file, it would cause
errors to locate that file anywhere in the fpath!
In another message, PWS said:
>
> By the way, you can use the trick of
>
> eval "$(which compdef)"
>
> to sync the line numbers with the which output. At least I hope so ---
> if this goes screwy there's a bug in text.c.
No, you can't. This causes all the lines to be numbered zero.
`zed -f' has the same problem; drives me nuts.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-07-07 23:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-05 5:33 Andrej Borsenkow
2001-07-06 9:56 ` Sven Wischnowsky
2001-07-06 10:22 ` Peter Stephenson
2001-07-07 23:30 ` Bart Schaefer [this message]
2001-07-08 22:26 ` Peter Stephenson
2001-07-09 10:38 ` Peter Stephenson
2001-07-09 14:52 ` Peter Stephenson
2001-07-09 16:30 ` Peter Stephenson
2001-07-09 16:50 ` Bart Schaefer
2001-07-09 17:32 ` Peter Stephenson
2001-07-09 18:24 ` Bart Schaefer
2001-07-09 18:36 ` Peter Stephenson
2001-07-09 19:19 ` 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=1010707233010.ZM16910@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).