Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #15930

Re: "wait" loses signals

From Robert Elz <kre@munnari.OZ.AU>
Newsgroups gnu.bash.bug
Subject Re: "wait" loses signals
Date 2020-02-20 22:55 +0700
Message-ID <mailman.1262.1582214187.2412.bug-bash@gnu.org> (permalink)
References (1 earlier) <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>

Show all headers | View raw


    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

Back to gnu.bash.bug | Previous | Next | Find similar


Thread

Re: "wait" loses signals Robert Elz <kre@munnari.OZ.AU> - 2020-02-20 22:55 +0700

csiph-web