Hi Martin,
thank you for your response.
On Fri, Feb 10, 2023 at 1:20 PM Martin Schulte
wrote:
> Hi Godmar!
>
> > For instance:
> >
> > gback@lat2022:~$ sleep 10 && echo yes
> > ^Z
> > [1]+ Stopped sleep 10
> > gback@lat2022:~$ fg
> > sleep 10
> > gback@lat2022:~$
> >
> > ...
>
Hi,
the students in my Systems course are currently working on their shell
assignment and of course are giving bash a spin to compare features. One
student pointed out that logical expressions such as `a` && `b` in bash
don't seem to work when `a` is stopped and resumed.
For instance:
gback@lat2
On Wed, Jul 1, 2020 at 10:58 AM Chet Ramey wrote:
>
> > Looking at the bash 5.0 code, I see some comments in the code about
> > strategies to protect the jobs array and other data structures from
> > arriving SIGCHLD signals, but I have questions about, for instance,
> these:
> >
> > - printable_
Hi,
I'm trying to understand what approach bash takes to async-signal safety in
its design.
Generally, programs that use signals (such as SIGCHLD or SIGALRM) must make
sure that
(a) they do not access state (such as variables) from within the signal
handler if such state could also be accessed f
On Mon, Jun 22, 2020 at 6:28 PM Chet Ramey wrote:
>
> >
> > Thank you for your reply. Could you share any insights why bash
> > doesn't follow POSIX in this regard, like zsh, but unlike ksh, tcsh,
> > and dash/ash?
>
> ksh93u+ 2012-08-01 on RHEL 7 does do this.
>
> tcsh isn't a POSIX shell, so I a
On Mon, Jun 22, 2020 at 5:19 PM Chet Ramey wrote:
>
> On 6/22/20 4:48 PM, Godmar Back wrote:
> > (Disclosure: I performed a search for terminal, terminal settings,
> > tcsetattr in the bash-bug mailing list, without finding a discussion.
> > My apologies if this is a kn
(Disclosure: I performed a search for terminal, terminal settings,
tcsetattr in the bash-bug mailing list, without finding a discussion.
My apologies if this is a known issue or was already discussed.)
Hi,
according to POSIX Part A, Base Definitions (line 726-728, pg 20, Part
A: Base Definitions-
