zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: dana <dana@dana.is>
Cc: Peter Stephenson <p.stephenson@samsung.com>,
	"zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: [BUG] Anonymous functions cause funcfiletrace to produce function-relative line numbers
Date: Sat, 16 Dec 2017 13:10:32 -0800	[thread overview]
Message-ID: <CAH+w=7ZMpGbduUgRw-N5pO-ArAUEptA=G3tN=u6kd7V4UcXH2g@mail.gmail.com> (raw)
In-Reply-To: <FDA58405-4654-4DFC-951F-7E467CF836B2@dana.is>

On Fri, Dec 15, 2017 at 10:45 AM, dana <dana@dana.is> wrote:
>
> tried it with the functions in separate files, and they look correct there
> too... unless you use ksh-style definitions.

Does the same thing happen whenever a function is defined like this --

>   % < puts
>   #
>   puts() {
>     #
>     #
>     panic
>   }

--  in an autoload file (zsh included)?  That is, if the function is
parsed as part of a larger function, so it isn't defined until the
surrounding function is executed, then I'm betting the line numbers
from the original file are lost.


  reply	other threads:[~2017-12-16 21:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20171210232854epcas2p2f9d4f0ac2ad31feb5a54d61da49e7140@epcas2p2.samsung.com>
2017-12-10 23:28 ` dana
2017-12-11  9:41   ` Peter Stephenson
2017-12-11 10:12     ` Peter Stephenson
2017-12-11 21:57       ` dana
2017-12-15 10:21         ` Peter Stephenson
2017-12-15 18:45           ` dana
2017-12-16 21:10             ` Bart Schaefer [this message]
2017-12-16 22:33               ` dana
2017-12-18  9:01             ` Peter Stephenson
2017-12-20 17:39               ` Peter Stephenson
2017-12-20 22:26                 ` dana

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='CAH+w=7ZMpGbduUgRw-N5pO-ArAUEptA=G3tN=u6kd7V4UcXH2g@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=dana@dana.is \
    --cc=p.stephenson@samsung.com \
    --cc=zsh-workers@zsh.org \
    /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).