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: Accessing the evaluated expression which caused an error
Date: Fri, 3 Sep 2021 10:14:08 -0700	[thread overview]
Message-ID: <CAH+w=7aT6rgWDnfr0A=j7nrv2PjQMDJddefRhTg_VrmU2YF_6w@mail.gmail.com> (raw)
In-Reply-To: <CAMP9c5mLwUce-23zmZAbCtHU+q-BzLbYTV482YcohXoj__ynZw@mail.gmail.com>

On Thu, Sep 2, 2021 at 6:43 PM Zach Riggle <zachriggle@gmail.com> wrote:
> I'm aware of funcsourcetrace, funcstack, and TRAPDEBUG /
> ZSH_DEBUG_CMD as well, but none of these contain the actual expression
> evaluated -- just the input to zsh.
> I know that zsh has the data internally, since "zsh -x" shows the
> fully-evaluated expression, so that data must be available somewhere,
> even if it's not exposed in a shell variable.

Hm.  What xtrace does is dump each individual shell word ... it just
happens to dump them in the order that puts them together as an
"expression".  But you'll notice it's not actually an expression, it's
just e.g. a single simple command.  In fact it's even a bit weird for
some structured commands (look at the output for a "case" statement
for example).

It's correct that none of this is captured in any sort of format that
would be usable by a shell script.  It never exists all at once in
such a format internally.

What exactly might you want captured?

  reply	other threads:[~2021-09-03 17:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03  1:42 Zach Riggle
2021-09-03 17:14 ` Bart Schaefer [this message]
2021-09-03 17:38   ` Zach Riggle
2021-09-04 20:08     ` Bart Schaefer
2021-09-05  0:26       ` Zach Riggle
2021-09-05  1:44         ` Lawrence Velázquez
2021-09-05  2:08         ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH+w=7aT6rgWDnfr0A=j7nrv2PjQMDJddefRhTg_VrmU2YF_6w@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=zachriggle@gmail.com \
    --cc=zsh-users@zsh.org \


* 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


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).