Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: Robert Elz <kre@munnari.OZ.AU>
Newsgroups: gnu.bash.bug
Subject: Re: "wait" loses signals
Date: Thu, 20 Feb 2020 22:55:45 +0700
Lines: 31
Approved: bug-bash@gnu.org
Message-ID: <mailman.1262.1582214187.2412.bug-bash@gnu.org>
References: <ab007cd0-d98a-1faa-4765-2399f5df74db@gigawatt.nl> <9b9d435b-3d2f-99bd-eb3d-4a676ce8927d@gigawatt.nl> <750d460d-b8a4-4157-1488-9f4d9f973715@redhat.com> <35034c85-fd5a-5034-a2d5-e3903888069d@case.edu> <16027.1582163732@jinx.noi.kre.to> <15836.1582214145@jinx.noi.kre.to>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: usenet.stanford.edu 1582214188 20383 209.51.188.17 (20 Feb 2020 15:56:28 GMT)
X-Complaints-To: action@cs.stanford.edu
Cc: chet.ramey@case.edu, Denys Vlasenko <dvlasenk@redhat.com>, bug-bash@gnu.org
To: Harald van Dijk <harald@gigawatt.nl>
Envelope-to: bug-bash@gnu.org
In-Reply-To: <ab007cd0-d98a-1faa-4765-2399f5df74db@gigawatt.nl>
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic]
X-Received-From: 2001:3c8:9009:181::2
X-BeenThere: bug-bash@gnu.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-bash>
List-Post: <mailto:bug-bash@gnu.org>
List-Help: <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID: <15836.1582214145@jinx.noi.kre.to>
X-Mailman-Original-References: <ab007cd0-d98a-1faa-4765-2399f5df74db@gigawatt.nl> <9b9d435b-3d2f-99bd-eb3d-4a676ce8927d@gigawatt.nl> <750d460d-b8a4-4157-1488-9f4d9f973715@redhat.com> <35034c85-fd5a-5034-a2d5-e3903888069d@case.edu> <16027.1582163732@jinx.noi.kre.to>
Xref: csiph.com gnu.bash.bug:15930

    Date:        Thu, 20 Feb 2020 09:16:05 +0000
    From:        Harald van Dijk <harald@gigawatt.nl>
    Message-ID:  <ab007cd0-d98a-1faa-4765-2399f5df74db@gigawatt.nl>

  | In that case, I think we can interpret the "when" in the description
  | of the trap command literally except when 2.11 overrides it.

I think it should be interpreted just like its normal English usage,
as in:

	when I win the lottery I am going to buy a Ferrari
or
	I am going to buy a Ferrari when I win the lottery

(which both say the same thing).

It doesn't mean that the instant the lottery winnings arrive (tomorrow
please!) I will be at the luxury imported car dealers, rather it states
a pre-cpndition which will trigger an event which is to follow, sometime,
thereafter.

Thus
	When one of the correspomding conditions arrises (standards
	speak for "when a signal has been delivered") the argument
	action shall be read and executed...

is "sometime after a signal has been delvered, run the trap action".

kre