Re: Writing to /dev/stderr overwrites xtrace data

>I enabled xtrace to try and debug a bash script running on a validation >server. The script stored its stdout and stderr to a log file. I expected >to see trace data in the log file, but instead found a single log > statement, >a bunch of NULL bytes, and the line '+ exit 1'. Thi

Writing to /dev/stderr overwrites xtrace data

Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKA

Re: Parameter expansion resulting empty treated as if it's not empty

On 10/30/19 7:12 AM, Oğuz wrote: > Since > > bash -c '${1##*""}' _ foo > > prints an empty line, I was expecting > > bash -c '${1##*"${1##*}"}' _ foo > > to print an empty line too, but instead it prints foo. Thanks for the report. The shell doesn't handle the second quoted string correctly. I

Re: '#' in here-doc

On 10/23/19 5:35 PM, Oğuz wrote: > After running this on bash 5.0.9: > > wc -c < # > EOF > > if I hit up arrow key, I get this: > > wc -c < # > > EOF > > (there is an extra blank line). Can't reproduce on bash 4.4.20 though Thanks for the report. I'll take a look. Chet -- ``The lyf so short

Re: Signal ignore flags unexpectedly reset after "trap ... EXIT"

On 10/18/19 10:49 AM, Isaac To wrote: > Dear Chet, > > I read your reply in the mailing list archive. Thanks a lot for the > explanation, I get much better ideas about what the shell wants to do for > me after reading it. Sorry that I have to reply to my own message rather > than yours. I'll su

Re: Binding Containing Escape Key Fails to Escape History Search

On 10/22/19 5:45 PM, sunnycemet...@gmail.com wrote: > Moreover, the history search should be closed when the cursor is moved > (e.g. as with the left arrow key bound to backward-char), but the cursor > does not move (even with “æ” bound directly to forward-word). Because that character doesn't ter

Re: Binding Containing Escape Key Fails to Escape History Search

On 10/21/19 10:56 PM, sunnycemet...@gmail.com wrote: > Given the following binding... > >> "æ": "\ef" > > ... should not pressing “æ” during a history search end the search--the > same as pressing Escape followed by “f”?  This does not happen with 5.0.3 > (screencast attached). Incremental searc

Re: Parameter expansion resulting empty treated as if it's not empty

2019-10-30 14:12:41 +0300, Oğuz: [...] > I was expecting > > bash -c '${1##*"${1##*}"}' _ foo > > to print an empty line too, but instead it prints foo. [...] > Is this a bug? Yes, In gdb, we see the ${1##*} expands to \177 (CTLNUL) as a result of quote_string(). And that's used as is in the ou

Re: Parameter expansion resulting empty treated as if it's not empty

First two command lines lack "echo", sorry On Wed, Oct 30, 2019 at 2:12 PM Oğuz wrote: > Since > > bash -c '${1##*""}' _ foo > > prints an empty line, I was expecting > > bash -c '${1##*"${1##*}"}' _ foo > > to print an empty line too, but instead it prints foo. > > Other shells I could find don

Parameter expansion resulting empty treated as if it's not empty

Since bash -c '${1##*""}' _ foo prints an empty line, I was expecting bash -c '${1##*"${1##*}"}' _ foo to print an empty line too, but instead it prints foo. Other shells I could find don't have this problem $ sh -c 'echo "${1##*"${1##*}"}"' _ bar $ ash -c 'echo "${1##*"${1##*}"}"' _ bar $