From: "Rocky Bernstein" <rocky.bernstein@gmail.com>
To: zsh-workers@sunsite.dk
Subject: Re: Getting source file and line number of a function.
Date: Mon, 11 Aug 2008 15:39:11 -0400 [thread overview]
Message-ID: <6cd6de210808111239v480710a2xbbf45b5fafa7cf59@mail.gmail.com> (raw)
In-Reply-To: <200808111932.m7BJWu1f008907@pws-pc.ntlworld.com>
funcsourcetrace contains entries for source'd files, right?
On Mon, Aug 11, 2008 at 3:32 PM, Peter Stephenson
<p.w.stephenson@ntlworld.com> wrote:
> "Rocky Bernstein" wrote:
>> Great! Let me know when code is committed into CVS which includes
>> tracking source calls, and I'll revise the zshdb code then.
>>
>> Ditto for instruction skipping and/or showing the command to be run.
>
> I've committed the source code tracing, but I decided "funcsourcetrace"
> was a better name than "funcfiletrace", since "file" doesn't really
> distinguish the purpose of the new variable. I've added a test and
> fixed a couple of additional bugs. The test is fairly simple and it's
> quite possible that extending it would reveal further problems.
>
> The instruction skipping using "setopt ERR_EXIT" is also there.
>
> --
> Peter Stephenson <p.w.stephenson@ntlworld.com>
> Web page now at http://homepage.ntlworld.com/p.w.stephenson/
>
next prev parent reply other threads:[~2008-08-11 19:39 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 [this message]
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
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=6cd6de210808111239v480710a2xbbf45b5fafa7cf59@mail.gmail.com \
--to=rocky.bernstein@gmail.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).