回复: Possible bug in bash

2023-01-16 Thread anonymous4feedb...@outlook.com
I am sorry I made a mistake in the first email. Bash printed foo= bar=v and all other shells printed foo=v bar=. It turns out I am using --posix to enable alias in bash, and that’s what makes the difference. # file test shopt -s expand_aliases 2>/dev/null alias al=' ' alias foo=bar al for foo in

Re: BASH_XTRACEFD=1 read variable stdout flushing?

2023-01-16 Thread Dave Drambus
Thanks for the explanation and the help! On Mon, Jan 16, 2023 at 1:53 PM Chet Ramey wrote: > On 1/16/23 12:36 PM, dave.dram...@gmail.com wrote: > > Configuration Information [Automatically generated, do not change]: > > Machine: x86_64 > > OS: linux-gnu > > Compiler: gcc > > Compilation CFLAGS:

Question about monitor mode / ignoreeof / EOF read

2023-01-16 Thread Steffen Nurpmeso
Hello. I am sorry to be here again, and it rather is a question than a bug report. But i thought .. better than not. On the dash list a FreeBSD programmer reported some problem with the monitor mode of dash (it turned out a FreeBSD /bin/sh commit from 2014, ([cd60e2c67d52, sh: Allow enabling job

Re: BASH_XTRACEFD=1 read variable stdout flushing?

2023-01-16 Thread Chet Ramey
On 1/16/23 12:36 PM, dave.dram...@gmail.com wrote: Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -g -O2 -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format

Re: BASH_XTRACEFD=1 read variable stdout flushing?

2023-01-16 Thread Emanuele Torre
Oops. > And there is no reason to not use it since any bash version that > supports BASH_XTRACEFD, also supports {var}<&fd syntax. Of course, I meant to say that there is no reason to use BASH_XTRACEFD=1 over exec {BASH_XTRACEFD}<&1 . I forgot to change this paragraph after moving the suggestio

Re: BASH_XTRACEFD=1 read variable stdout flushing?

2023-01-16 Thread Greg Wooledge
On Mon, Jan 16, 2023 at 11:36:18AM -0600, dave.dram...@gmail.com wrote: > hence `set -x`, but I want the output to go to stdout rather than > stderr so > that cron emails me only when there is an actual failure. With this Cron sends email if there's any output on either stdout or stde

Re: BASH_XTRACEFD=1 read variable stdout flushing?

2023-01-16 Thread Emanuele Torre
On Mon, Jan 16, 2023 at 11:36:18AM -0600, dave.dram...@gmail.com wrote: > Description: > > I have `set -x` and `BASH_XTRACEFD=1` set in a simple script that I > have in > a cron job. I'd like to see the progress of the script when run > manually, > hence `set -x`, but I want th

Re: Possible bug in bash

2023-01-16 Thread Chet Ramey
On 1/15/23 7:42 AM, anonymous4feedb...@outlook.com wrote: For the follow script alias al=' ' alias foo=bar al for foo in v do echo foo=$foo bar=$bar done bash (version 5.1.16) prints foo=v bar=, while all other shells I tested (dash, ksh, zsh, and yash) all prints foo= bar=v. That's strange. I

BASH_XTRACEFD=1 read variable stdout flushing?

2023-01-16 Thread dave . drambus
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -g -O2 -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wall uname output: Linux sulfur 5.15.0-5

Re: SIGINT handling during async functions

2023-01-16 Thread Chet Ramey
On 1/12/23 6:34 PM, Tycho Kirchner wrote: Hi, we found quite some inconsistency and weirdness in the handling of SIGINT's during async function calls and were wondering, whether those are expected. All calls were executed from a script with jobcontrol turned off (set +m) while pressing Ctrl+C