From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh workers <zsh-workers@zsh.org>
Subject: TRY_BLOCK_ERROR and exit status
Date: Sun, 23 Nov 2014 11:57:55 -0800 [thread overview]
Message-ID: <141123115755.ZM10874@torch.brasslantern.com> (raw)
In-Reply-To: <CAHYJk3RpnsauBYHw1QHbvpsTfM+0oSih_7diJTm2Ybp9xLYOxw@mail.gmail.com>
On Nov 23, 7:08pm, Mikael Magnusson wrote:
}
} % { $(< foo) } always { TRY_BLOCK_ERROR=0 }; echo hello
} zsh: no such file or directory: foo
} hello
}
} However, I'm not sure how to
} make the construct return false when it failed with a fatal error.
Arguably a fatal error should set both errflag and lastval nonzero, but
that might require a lot of tiny changes all over the place ... on the
other hand I think always+TRY_BLOCK_ERROR is the only way lastval can
still be examined after errflag has been set, so maybe it would suffice
to handle this there?
What should the value of lastval ($?) be in this circumstance?
next prev parent reply other threads:[~2014-11-23 19:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-22 17:13 BUG: failure in "vcs_info prompt" aborts precmd function Daniel Hahler
2014-11-22 17:20 ` [PATCH] vcs_info: test -f .git/rebase-merge/done before reading it Daniel Hahler
2014-11-22 17:51 ` BUG: failure in "vcs_info prompt" aborts precmd function Mikael Magnusson
2014-11-22 18:01 ` Daniel Hahler
2014-11-22 22:20 ` Mikael Magnusson
2014-11-22 22:44 ` Bart Schaefer
2014-11-23 19:02 ` Peter Stephenson
2014-11-23 19:38 ` Bart Schaefer
2014-11-23 20:04 ` Peter Stephenson
2014-11-23 15:58 ` Daniel Hahler
2014-11-23 18:08 ` Mikael Magnusson
2014-11-23 19:57 ` Bart Schaefer [this message]
2014-11-24 10:11 ` TRY_BLOCK_ERROR and exit status Peter Stephenson
2014-11-25 8:01 ` Bart Schaefer
2014-11-25 9:18 ` Peter Stephenson
2014-11-23 18:13 ` BUG: failure in "vcs_info prompt" aborts precmd function Bart Schaefer
2014-11-23 18:52 ` Mikael Magnusson
2014-11-23 19:47 ` Bart Schaefer
2014-11-23 22:03 ` Oliver Kiddle
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=141123115755.ZM10874@torch.brasslantern.com \
--to=schaefer@brasslantern.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).