zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@sunsite.dk
Subject: Re: Getting source file and line number of a function.
Date: Wed, 13 Aug 2008 21:51:38 +0100	[thread overview]
Message-ID: <20080813215138.2f16e81d@pws-pc> (raw)
In-Reply-To: <2d460de70808110700x1dcd6460i94327cbf0315f17a@mail.gmail.com>

On Mon, 11 Aug 2008 16:00:21 +0200
"Richard Hartmann" <richih.mailinglist@gmail.com> wrote:
> On Sat, Aug 9, 2008 at 20:21, Peter Stephenson
> <p.w.stephenson@ntlworld.com> wrote:
> 
> [stuff about $funcfiletrace]

(which now really is called that...)

> This just gave me an idea: Why not enhance `whence` so it is able to
> tell in what file and starting on what line a function has been defined?

Just to note I haven't forgot this yet (haven't looked at if or where it
fits without messing up the format).  I think it would be useful to
provide an associative array in zsh/parameter with this information to
get at it easily, something like $functionsources (since the assoc
array with the functions is called $functions).

-- 
Peter Stephenson <p.w.stephenson@ntlworld.com>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/


      reply	other threads:[~2008-08-13 20:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-27  1:06 Rocky Bernstein
2008-07-28  8:34 ` Peter Stephenson
2008-07-28 12:46   ` Rocky Bernstein
2008-07-30  2:31     ` Rocky Bernstein
2008-07-30  8:22       ` Peter Stephenson
2008-08-09 18:21     ` Peter Stephenson
2008-08-10  1:11       ` Rocky Bernstein
2008-08-11 19:32         ` Peter Stephenson
2008-08-11 19:39           ` Rocky Bernstein
2008-08-11 19:51             ` Peter Stephenson
2008-08-11 20:01               ` Rocky Bernstein
2008-08-11 14:00       ` Richard Hartmann
2008-08-13 20:51         ` Peter Stephenson [this message]

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=20080813215138.2f16e81d@pws-pc \
    --to=p.w.stephenson@ntlworld.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).