Re: doc-strings of the 'command' built-in, as output by help

n. > > -VFor each COMMAND, print a more verbose description of how it would be interpreted if used as a command name, similar to the 'type' built-in. - Andrew

doc-strings of the 'command' built-in, as output by help

ting) container running under LXD on ChromeOS Best, Andrew -- Andrew D. Davis, PhD PGP Key <https://www.openpgp.org/about>: 0xC1665F6A

Bash ONESHOT optimization in conjunction with interactive mode breaks

Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -g -O2 -Wno-parentheses -Wno-format-security uname output: Linux nas 5.15.85 #1-NixOS SMP Wed Dec 21 16:36:38 UTC 2022 x86_64 GNU/Linux Machine Type: x86_64-pc-l

Exit trap changes return value of subshell for uncaught trap signals

Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -s

Re: caller returns wrong line number in command substitution

t: Tuesday, October 18, 2022 7:09 PM To: Andrew Neff Cc: bug-bash@gnu.org Subject: Re: caller returns wrong line number in command substitution There are no command substitutions in any of your examples. A command substitution is what you get with $( ) (or if you really like obsolete syntax for s

caller returns wrong line number in command substitution

Machine: x86_64 OS: linux-musl Compiler: gcc Compilation CFLAGS: -g -O2 uname output: Linux cfa1574b05c7 5.10.102.1-microsoft-standard-WSL2 #1 SMP Wed Mar 2 00:30:59 UTC 2022 x86_64 GNU/Linux uname output: Linux 3beae0f31cdf 5.18.18-100.fc35.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Aug 17 16:09:22 UTC 2

Re: Bash reference manual feedback

rs that it's telling >you to avoid. I suspect the intent here was to point out the use of the "smart quote" (U+2019) instead of the intended ASCII single quote (U+0027). --Andrew Church https://achurch.org/

Re: Unfortunate error message for invalid executable

Awesome (I made no claims of expertise about the details of the call semantics). I agree any multi-call scenario would among other things not be atomic. Though, I’m not sure that’s what you mean by hoodwinked. That last suggestion is exactly one I also made (simply improve the error text) and I

Re: Unfortunate error message for invalid executable

I’ll give it a shot. A. > On May 28, 2022, at 4:35 PM, Dale R. Worley wrote: > > AA via Bug reports for the GNU Bourne Again SHell > writes: >> I.e., something like "I'm not sure what's going on, but your path >> definitely exists, yet the kernel says otherwise." >> >> ... something like fp

[PATCH] Avoid pronouns in documentation

e bad ones, you're asking the wrong question.") I've left pronouns referring to specific individuals unchanged, on the assumption that those pronouns are correct for those individuals. --Andrew Church http://achurch.org/ diff --git a/doc/bashref.texi b/doc/bashref.texi inde

Re: Bash parameter transforamtion on empty array triggers unset variable.

avior, and it seems to me the ${x@a} should definitely work here, with nounset turns on 3. The same as #2, but for associative arrays Works: (set -eu; declare -A x=(); echo "${x[@]}") Does not work, but should: (set -eu; declare -A x=(); echo "${x@a}") Thanks On Tue, Aug 11,

Bash parameter transforamtion on empty array triggers unset variable.

Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-musl Compiler: gcc Compilation CFLAGS: -g -O2 -Wno-parentheses -Wno-format-security uname output: Linux 28e237a5e16f 5.5.7-200.fc31.x86_64 #1 SMP Fri Feb 28 17:18:37 UTC 2020 x86_64 GNU/Linux Machine Type:

Re: Backspace echoed incorrectly with TERM=garbage

dline against ncurses-5.9 (forcing -lncurses), the problem goes away: read(0, "\177", 1) = 1 write(2, "\10 \10", 3) = 3 So the problem may be either in ncurses itself or in readline's interaction with ncurses/libtinfo. --Andrew Church http://achurch.org/

Re: set -e ignored in subshell if part of command list

-OR list in rule 2 should be treated differently, and absent an explicit requirement one way or the other, I think the expected behavior here would be that the behavior of the subshell is independent of the subshell's context in the parent shell. --Andrew Church http://achurch.org/

Re: Writing to /dev/stderr overwrites xtrace data

trace log lines which were previously written. Bash still has an open file descriptor to stderr, which has its own seek position, so if you add another command (like "exit 1") to the generated script after the echo, the xtrace line generated by that command will be written at that positi

Re: bash sets O_NONBLOCK on pts

ted program sets O_NONBLOCK on stdin and then exits, that state will remain until some other program unsets it. For example: $ cat >foo.c #include int main(void) {fcntl(0, F_SETFL, O_NONBLOCK); return 0;} ^D $ cc foo.c $ ./a.out $ cat cat: -: Resource temporarily unavailable --Andrew Church http://achurch.org/

Re: Use high bits of the raw random number?

in the output is from dieharder and is irrelevant -- the generator was seeded with the value 1 in all cases). --Andrew Church http://achurch.org/ $ bashrand-low16

Re: Valgrind detects invalid read in bash. malloc assertion fails.

lso avoid this false positive. (Strictly speaking, even the renaming of "free" to "sh_xfree" in xmalloc.h results in undefined behavior by the above rule, but that at least is resolved at compilation time, and I presume there are no real-world build environments in which that renaming causes a problem.) --Andrew Church http://achurch.org/

Re: Segfault after many stackframes

e to say 'stack overflow'. That's exactly what bash is saying there. I'm not sure what (if anything) POSIX specifies for stack overflow behavior, but at least on Linux, stack overflow raises SIGSEGV: $ echo 'int main(void) {return main();}' | cc -o foo -x c -

Re: bash-5.0_p1: wildcard expansion bug with unreadable intermediate directories

/* "/tmp/a/b"/* /tmp/a/b/c /tmp/a/b/c /tmp/a/b/* --Andrew Church http://achurch.org/

bash-5.0_p1: wildcard expansion bug with unreadable intermediate directories

b"/* /tmp/a/b/c /tmp/a/b/c bash-5.0$ chmod -r /tmp/a bash-5.0$ echo /tmp/a/b/* "/tmp/a/"b/* "/tmp/a/b"/* /tmp/a/b/c /tmp/a/b/* Note how the third expansion in the last command fails even though /tmp/a/b is readable. --Andrew Church http://achurch.org/

arithmetic problem, incorrect return code with ((var++)) when var is 0 before operation

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' -DPACKAGE

Re: bash 4.4: `configure --enable-static-link --without-gnu-malloc` fails with `No rule to make target 'install-'`

On Mon, Oct 3, 2016 at 10:57 AM, Chet Ramey wrote: > On 10/3/16 10:01 AM, Chet Ramey wrote: > > On 10/2/16 6:54 PM, Andrew Tomazos wrote: > >> When I try to configure and make install bash 4.4 as follows: > >> > >> $ configure --enable-static-link --wi

bash 4.4: `configure --enable-static-link --without-gnu-malloc` fails with `No rule to make target 'install-'`

is causing SHOBJ_STATUS to be empty at this point in the build. Any ideas? Thanks, Andrew.

improper bashrc sourcing with closed stdin

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-unknown-linux-gnu' -DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/share/local

bind command dies on bad syntax

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

Re: bash cross with installed readline

o use AC_TRY_COMPILE. Unfortunately I have not enough time now but I hope I will find time slot for this in the nearest weeks. Best Regards, Andrey K. On Wed, Mar 19, 2014 at 7:29 AM, Mike Frysinger wrote: > On Sun 16 Mar 2014 13:30:55 Andrew Kosteltsev wrote: > > When we build bash for so

bash cross with installed readline

Dear All, When we build bash for some targets the INCLUDES variable for BUILD_CC contains the path to target readline headers. This path points to the target headers which not preferred for utilities which prepared for build machine. Also when we have installed readline on the target the configur

Re: FW: multi-line alias executed out of order

1410711 ubuntu@ubuntu:~$ foo2 one 11.805819275 four 11.819741270 three 11.828260887 two 11.829470548 Fix: Use a single-line alias. Or use the "&&" operator to chain commands (which changes the functionality to be short-circuit evaluations). Also verified this behavior on RHEL6 with bash 4

multi-line alias executed out of order

89three 09.749212492four 09.761410711ubuntu@ubuntu:~$ foo2one 11.805819275four 11.819741270three 11.828260887two 11.829470548 Fix: Use a single-line alias. Or use the "&&" operator to chain commands (which changes the functionality to be short-circuit evaluations). Also verified this behavior on RHEL6 with bash 4.1.2(1). Thanks!Andrew Martin

bash-source closes file descriptor before reading from it on Darwin

Configuration Information [Automatically generated, do not change]: Machine: i386 OS: darwin12.4.0 Compiler: cc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' -DCONF_OSTYPE='darwin12.4.0' -DCONF_MACHTYPE='i386-apple-darwin12.4.0' -DCONF_VENDOR='apple' -DLOCALEDIR='/usr/local/Cellar/ba

Re: HP-UX exec tee hanging/not working intermittently

On Tue, Jul 31, 2012 at 4:55 AM, Greg Wooledge wrote: > On Mon, Jul 30, 2012 at 02:17:15PM -0700, Andrew Resch wrote: >> I am attempting to use exec and tee to have my scripts >> stdout/stderr appended to a log file like such: exec > >(tee -a $LOG) >> 2>&a

HP-UX exec tee hanging/not working intermittently

Configuration Information [Automatically generated, do not change]: Machine: ia64 OS: hpux11.31 Compiler: cc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='ia64' -DCONF_OSTYPE='hpux11.31' -DCONF_MACHTYPE='ia64-hp-hpux11.31' -DCONF_VENDOR='hp' -DLOCALEDIR='/u sr/local/share/locale' -DPACKAGE

weird behaviour of ((count++)) when using , , to change to lower case

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-unknown-linux-gnu' -DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/share/local

Re: inconsistent exit status of ((count++))

On 30/07/10 19:55, Stefano Lattarini wrote: At Thursday 29 July 2010, Andrew Benton wrote: andy:~$ count=0 andy:~$ ((count++)) andy:~$ echo $? 1 andy:~$ ((count++)) andy:~$ echo $? 0 I don't think it's a bug, it's just an effect of: 1. `((EXPR))' returning a non-zero

inconsistent exit status of ((count++))

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-unknown-linux-gnu' -DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/share/loca

Re: Bash 2.05a isn't calling gawk as expected

On Tue, Nov 06, 2007 at 04:30:20PM -0500, [EMAIL PROTECTED] wrote: > #!/bin/sh > > blockflag=/ihome/tables/modemhog.txt > pageflag=/ihome/tables/modemhog.page > > [ -s $blockflag ] && exit > > for i in /home/* > do > [ -d $i ] || continue > cd $i > > [ -f session_log ] || continue > >

RE: bash does not handle escape sequences for inserted paramaters to for

This will work $ eval "for i in $(echo a b\\ c); do echo \"\$i\"; done" a b c http://lists.gnu.org/archive/html/bug-bash/2007-07/msg00011.html ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash

RE: wrong logical evaluation of expressions involving true or falsecommands

'help test' says that an expression consisting of a single string is an alias for "-n STRING" which is "true if the string is not empty." So, [ false -a false ] and [ false ] are true because "false" is a non-empty string. [ "" ] is false. You probably just want 'true && false' without the [.

Re: NOT changing global variables

you should pick a naming convention for variable names you intend to pass. Otherwise local function variables may collide. "data" in place of "a" would be a bad choice in the above example :-) There may also be technical limitations to using eval like this. If there are, Im

Re: Segmentation faults with 64bit bash on sparc64 linux

ply. Park this for a moment; I am nearly convinced this problem is down to the sparc64 linux kernel being miscompiled by gcc-4.1.1. I'm in the middle of running some tests using a kernel built with a patched compiler; so far, everything is working fine, but I'll let you know the outcome

Re: Segmentation faults with 64bit bash on sparc64 linux

x00196a90 in siglongjmp () #1 0x00205cac in _dl_signal_error () (gdb) > > Andrew Walrond ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash

Segmentation faults with 64bit bash on sparc64 linux

e' phase of building gcc-4.1.1, the Makefile runs various configure scripts. Here is a typical failure: Links are now set up to build a native compiler for sparc64-unknown-linux-gnu. updating cache ./config.cache configure: creating ./config.status /home/andrew/dump/gcc-4.1.

Python and Bash

Not exactly a bug, perse. An oddity, however. I am writing some code in bash that will execute a python script, and carry on with some user input. Obivously, I called the python command through something like ( python test.py test.txt ) in order for it to be a process. However, this test.py progr

locally declared arrays do not act as arrays

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

Shell completion not honouring escaped characters

BASH_VERSION 3.1.1(1)-release Running on Fedora Core 5 (test 2) Pressing tab on a line with escape characters will ignore, and remove, the escaped characters to perform the completion. For example, pressing tab at the end of each of these lines removes the "\" and changes the meaning of the l

Re: Developement

Norman Virus Control a supprimé le message original qui contenait le virus [EMAIL PROTECTED] ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash