zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zach Riggle <zachriggle@gmail.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Source mangling in $functions_source and typeset -f
Date: Sat, 27 Nov 2021 09:47:23 -0800	[thread overview]
Message-ID: <CAH+w=7bkxmP9rVeiMObYBXpeayY2Hf8qDRp6r_570wkE3ZdQHA@mail.gmail.com> (raw)
In-Reply-To: <CAMP9c5n-hGj5ifk9KDZM29=e1u8m6nLDhxtsNgsqHKr7mLALcQ@mail.gmail.com>

On Sat, Nov 27, 2021 at 12:02 AM Zach Riggle <zachriggle@gmail.com> wrote:
>
> Unfortunately, "$functions_source[foo]" and "typeset -f foo" both seem to remove all comments, and rewrite the source such that there's no empty newlines

With the exception of the contents of strings (including
here-documents), the original source of a function is not kept in
shell memory.  Instead a parse tree is stored and used to regenerate
the function definition by "typeset -f" et al.  Comments and
semantically-meaningless whitespace are discarded during parsing,
hence they're not available later.

> Is there a convenient way, from within zsh, to get either:
>
> The original, unmodified source of a function (autoloaded or otherwise)
> The line offsets in the file where the function is defined (if any)?

The parse tree only tracks the line numbers of executable code, so as
to be able to update the LINENO variable and print line numbers in
debug traces and prompts.  The line number of the closing brace isn't
recorded (in fact it's possible to define a function without any open
or close brace if the body is a single expression).

So, strictly speaking, no, neither of those.


  reply	other threads:[~2021-11-27 17:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-27  8:01 Zach Riggle
2021-11-27 17:47 ` Bart Schaefer [this message]
2021-11-27 19:25   ` Ray Andrews
2021-11-27 19:40     ` Lawrence Velázquez
2021-11-27 20:09       ` Ray Andrews
2021-11-27 20:14     ` Bart Schaefer
2021-11-27 21:56       ` Ray Andrews
2021-11-29 16:00   ` Peter Stephenson
2021-11-29 17:55     ` Bart Schaefer
2021-12-01  6:53       ` Daniel Shahaf

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=7bkxmP9rVeiMObYBXpeayY2Hf8qDRp6r_570wkE3ZdQHA@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=zachriggle@gmail.com \
    --cc=zsh-users@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).