Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

PATCH: $signals

X-seq: zsh-workers 37127
From: Peter Stephenson <p.stephenson@xxxxxxxxxxx>
To: Zsh Hackers' List <zsh-workers@xxxxxxx>
Subject: PATCH: $signals
Date: Tue, 17 Nov 2015 10:27:45 +0000
List-help: <mailto:zsh-workers-help@zsh.org>
List-id: Zsh Workers List <zsh-workers.zsh.org>
List-post: <mailto:zsh-workers@zsh.org>
Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
Organization: Samsung Cambridge Solution Centre

Musing for the Nth time on how we managed to design the $signals array
so that indices are off by one from signals, I noticed we don't even
document the fact.

pws

diff --git a/Doc/Zsh/params.yo b/Doc/Zsh/params.yo
index b896e2d..00ee41f 100644
--- a/Doc/Zsh/params.yo
+++ b/Doc/Zsh/params.yo
@@ -771,7 +771,13 @@ Incremented by one each time a new shell is started.
 )
 vindex(signals)
 item(tt(signals))(
-An array containing the names of the signals.
+An array containing the names of the signals.  Note that with
+the standard zsh number of array indices, where the first element
+has index 1, the signals are offset by 1 from the signal number
+used by the operating system.  For example, on typical Unix-like systems
+tt(HUP) is signal number 1, but is referred to as tt($signals[2]).  This
+is because of tt(EXIT) at position 1 in the array, which is used
+internally by zsh but is not known to the operating system.
 )
 vindex(TRY_BLOCK_ERROR)
 item(tt(TRY_BLOCK_ERROR) <S>)(

Messages sorted by: Reverse Date, Date, Thread, Author