zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <danielsh@apache.org>
To: zsh-workers@zsh.org
Subject: [PATCH 2/2] zshmisc(1): Fix markup of "try-list" and "always-list".
Date: Sat, 21 Dec 2019 12:41:04 +0000	[thread overview]
Message-ID: <20191221124104.22751-2-danielsh@apache.org> (raw)
In-Reply-To: <20191221124104.22751-1-danielsh@apache.org>

---
 Doc/Zsh/grammar.yo | 24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/Doc/Zsh/grammar.yo b/Doc/Zsh/grammar.yo
index a66358ed6..e028c8512 100644
--- a/Doc/Zsh/grammar.yo
+++ b/Doc/Zsh/grammar.yo
@@ -313,23 +313,23 @@ An `error' in this context is a condition such as a syntax error which
 causes the shell to abort execution of the current function, script, or
 list.  Syntax errors encountered while the shell is parsing the
 code do not cause the var(always-list) to be executed.  For example,
-an erroneously constructed tt(if) block in tt(try-list) would cause the
-shell to abort during parsing, so that tt(always-list) would not be
+an erroneously constructed tt(if) block in var(try-list) would cause the
+shell to abort during parsing, so that var(always-list) would not be
 executed, while an erroneous substitution such as tt(${*foo*}) would
-cause a run-time error, after which tt(always-list) would be executed.
+cause a run-time error, after which var(always-list) would be executed.
 
 An error condition can be tested and reset with the special integer
-variable tt(TRY_BLOCK_ERROR).  Outside an tt(always-list) the value is
-irrelevant, but it is initialised to tt(-1).  Inside tt(always-list), the
-value is 1 if an error occurred in the tt(try-list), else 0.  If
-tt(TRY_BLOCK_ERROR) is set to 0 during the tt(always-list), the error
-condition caused by the tt(try-list) is reset, and shell execution
-continues normally after the end of tt(always-list).  Altering the value
-during the tt(try-list) is not useful (unless this forms part of an
+variable tt(TRY_BLOCK_ERROR).  Outside an var(always-list) the value is
+irrelevant, but it is initialised to tt(-1).  Inside var(always-list), the
+value is 1 if an error occurred in the var(try-list), else 0.  If
+tt(TRY_BLOCK_ERROR) is set to 0 during the var(always-list), the error
+condition caused by the var(try-list) is reset, and shell execution
+continues normally after the end of var(always-list).  Altering the value
+during the var(try-list) is not useful (unless this forms part of an
 enclosing tt(always) block).
 
-Regardless of tt(TRY_BLOCK_ERROR), after the end of tt(always-list) the
-normal shell status tt($?) is the value returned from tt(try-list).
+Regardless of tt(TRY_BLOCK_ERROR), after the end of var(always-list) the
+normal shell status tt($?) is the value returned from var(try-list).
 This will be non-zero if there was an error, even if tt(TRY_BLOCK_ERROR)
 was set to zero.
 

  reply	other threads:[~2019-12-21 12:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-21 12:41 [PATCH 1/2] zshmisc(1): Clarify the documentation of 'return' and 'exit' in conjunction with try/always Daniel Shahaf
2019-12-21 12:41 ` Daniel Shahaf [this message]
2019-12-21 17:58 ` Peter Stephenson
2019-12-22  3:10   ` 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=20191221124104.22751-2-danielsh@apache.org \
    --to=danielsh@apache.org \
    --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).