On 2/7/23 9:00 AM, Emanuele Torre wrote:
Before this patch, if allexport was set, $_ gained the "x" attribute
after PROMPT_COMMAND finished running, that would only get removed after
the next simple command is executed.
Thanks for the report. This is a good fix.
--
``The lyf so short, the craf
On 2/6/23 10:26 PM, Martin D Kealey wrote:
By orthogonal, I meant these things should ideally be managed by separate
controls:
1. ignoring signals (or not)
2. redirecting filedescriptors
3. immediately waiting on the process (or not)
4. creating new process groups
5. sending a signal t
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
Hi Godmar!
> For instance:
>
> gback@lat2022:~$ sleep 10 && echo yes
> ^Z
> [1]+ Stopped sleep 10
> gback@lat2022:~$ fg
> sleep 10
> gback@lat2022:~$
>
> ...
>
> What's the rationale for bash's behavior in this case and is this something
> that should be changed?
I assume this
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:~$
> >
> > ...
>
On Feb 10 2023, Godmar Back wrote:
> It appears to be mistaking the wait status for the exit status if your
> hypothesis is correct.
Easy to verify:
$ sleep 10 && echo yes || echo $?
^Z
[1]+ Stopped sleep 10
148
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 75
