Re: internal error

2024-02-12 Thread Frank Heckenbach
> On 2/10/24 9:41 PM, Frank Heckenbach wrote: > > % ./bash -c "set -e; f() { eval false; }; f" > > ./bash: line 1: pop_var_context: head of shell_variables not a function > > context > > > > Might be related to > > https://lists.gnu.org/archive/h

internal error

2024-02-10 Thread Frank Heckenbach
% ./bash -c "set -e; f() { eval false; }; f" ./bash: line 1: pop_var_context: head of shell_variables not a function context Might be related to https://lists.gnu.org/archive/html/bug-bash/2022-10/msg00073.html, but still present in 5.2.21.

Re: Missing documentation "-bash_input"

2023-11-28 Thread Klaus Frank
23-11-29 01:27:17, Lawrence Velázquez wrote: On Tue, Nov 28, 2023, at 5:33 PM, Klaus Frank wrote: sorry, but this is not true It is true. I can clearly see that it exists. It may be an distro addition though. Is it specific to ArchLinux? Because I can see it being used and when I try to use it

Re: Missing documentation "-bash_input"

2023-11-28 Thread Klaus Frank
"$copydir" "${bindmounts_ro[@]}" "${bindmounts_rw[@]}" \    bash -c 'yes y | pacman -U -- "$@"' -bash "${pkgnames[@]/#//root/}" Bash source code on GitHub mirror: https://github.com/bminor/bash/blob/master/y.tab.c#L3967 "(--bas

Missing documentation "-bash_input"

2023-11-28 Thread Klaus Frank
eful when calling bash has to be wrapped within another command like chroot E.g. `chroot /path /bin/bash -c "echo $@" -bash "pipe input"` ``` Yours sincerely, Klaus Frank smime.p7s Description: S/MIME Cryptographic Signature

Re: executes statement after "exit"

2022-04-15 Thread Frank Heckenbach
> > #!/bin/bash > > : $((08 + 0)); exit > > echo "Should not get here." > > It never executes `exit'. > > The explanation in > https://lists.gnu.org/archive/html/bug-bash/2022-04/msg00010.html applies > here. > > The arithmetic syntax error (invalid octal constant) results in a word > expansio

executes statement after "exit"

2022-04-15 Thread Frank Heckenbach
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall uname output: Linux mars 5.10.0-12-amd64 #1 SMP Debian 5.10.103-1 (2022-03-07) x86_64 GNU/Lin

Re: "trap" output from "if" statement redirected wrongly

2022-04-13 Thread Frank Heckenbach
> On Wed, Apr 13, 2022 at 7:59 AM Frank Heckenbach > wrote: > > This script writes "foo" to bar rather than stdout as I'd expect. > > > > It's triggered by the "if" statement (which doesn't even cause > > running in a subshell, so

"trap" output from "if" statement redirected wrongly

2022-04-13 Thread Frank Heckenbach
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall uname output: Linux mars 5.10.0-12-amd64 #1 SMP Debian 5.10.103-1 (2022-03-07) x86_64 GNU/Lin

Re: Corrupted multibyte characters in command substitutions fixes may be worse than problem.

2022-02-07 Thread Frank Heckenbach
> In the case of bash with environment having LC_CTYPE: C.UTF-8 or > en_US.UTF-8 > read: > 0xC3 (len=1) i.e. Ã ('A' w/tilde in a legacy 8-bit latin-compatible > charset), > but invalid if bash processes the environment setting of en_US.UTF-8. > > Should bash process it as legacy input or invali

Re: Corrupted multibyte characters in command substitutions fixes may be worse than problem.

2022-02-06 Thread Frank Heckenbach
> On 2022/01/02 17:43, Frank Heckenbach wrote: > > > Why would you? Aren't you able to assess the severity of a bug > > yourself? Silent data corruption is certainly one of the most severe > > kind of bugs ... > --- > That's debatable, BTW, as I was reminde

Re: Corrupted multibyte characters in command substitutions

2022-01-07 Thread Frank Heckenbach
t;, which you discarded to get a more thorough one. Well, the hard part was the analysis. After I found the problem, the fix then wasn't that hard either way. > I was impressed as well by your careful analysis. > > Chet, I think you should consider if Frank patch isn't better t

Re: Corrupted multibyte characters in command substitutions

2022-01-02 Thread Frank Heckenbach
nly a bug is reported and someone needs to find the cause and fix it, but when the patch is there and tested, it's a matter of minutes (if you have a moderately sane build system) to apply it and save your users a lot of trouble. Frank

Re: Corrupted multibyte characters in command substitutions

2022-01-02 Thread Frank Heckenbach
Chet Ramey wrote: > On 1/1/22 7:02 PM, Frank Heckenbach wrote: > > Thanks for the report. This is a pretty good in-depth analysis of the issue. > > This was fixed back in March, 2021 in the devel branch as a result of > https://savannah.gnu.org/patch/?10035 (though the fix

Corrupted multibyte characters in command substitutions

2022-01-01 Thread Frank Heckenbach
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall uname output: Linux mars 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux

Re: declare(1) not executing inside source'd script

2018-07-27 Thread Frank Edwards
never ran. The which command didn’t help, but whereis tracked down the duplicate. Thanks again for your time (this was embarrassing, as I know better :)). <http://www.eeconsulting.net/> Edwards & Edwards Consulting, LLC <http://www.eeconsulting.net/> Frank J. Edwards sa...@e

Re: declare(1) not executing inside source'd script

2018-07-27 Thread Frank
shell? I will not use section numbers in the future. :) -- Frank Edwards Edwards & Edwards Consulting, LLC Hours: 10A-6P ET Phone: (813) 406-0604 Sent from my iPhone. No electrons were harmed in the creation or transmission of this message. > On Jul 27, 2018, at 10:17 AM, Greg Wooledge

Re: declare(1) not executing inside source'd script

2018-07-27 Thread Frank
Agreed. But the bash installation does create a man page for it, does it not? So a command like, “man 1 declare” does work...? I always thought this was somewhat incongruous. -- Frank Edwards Edwards & Edwards Consulting, LLC Hours: 10A-6P ET Phone: (813) 406-0604 Sent from my iPhone.

declare(1) not executing inside source'd script

2018-07-27 Thread frank
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-redhat-linux-gnu' -DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale'

Re: feature request: file_not_found_handle()

2013-08-21 Thread Andreas Gregor Frank
Hi Eduardo, thank you very much for this constructive and honest answer. Not what i hoped to see, but this is only a request. For me only a nice to have...so fine bye Andreas 2013/8/21 Eduardo A. Bustamante López > On Wed, Aug 21, 2013 at 08:39:53PM +0200, Andreas Gregor Frank wr

Re: feature request: file_not_found_handle()

2013-08-21 Thread Andreas Gregor Frank
Hello Greg, this is a feature request for no_such_file_or_directory_ handle(). I do not want to talk about missing quotes in anyone's code example! And the question if it makes sense to implement a command_not_found_handle() in this or that way has nothing to do with this request, too. How someone

Re: feature request: file_not_found_handle()

2013-08-19 Thread Andreas Gregor Frank
ethod... So at the moment slashes are forbidden in object names in my fun project. Now you know why your bash example for ckexec() isn't a solution for me. bye Andreas 2013/8/19 Chet Ramey > On 8/19/13 6:57 AM, Andreas Gregor Frank wrote: > > Hi Chet, > > > > I have no

Re: feature request: file_not_found_handle()

2013-08-19 Thread Andreas Gregor Frank
mey > On 8/14/13 7:44 AM, Andreas Gregor Frank wrote: > > Hi, > > > > i think a file_not_found_handle() or a modified > command_not_found_handle(), > > that does not need an unsuccessful PATH search to be triggered, would be > > useful and consistent. >

Re: feature request: file_not_found_handle()

2013-08-17 Thread Andreas Gregor Frank
Hi Ken, same reason for me: some object-oriented shell ( http://oobash.sourceforge.net/) "But given that the first entry on a command line pretty much has to be a command, I'm not sure it makes sense to invoke file_not_found_handle()" I think you are right. But then we go in circles...: http://

feature request: file_not_found_handle()

2013-08-14 Thread Andreas Gregor Frank
Hi, i think a file_not_found_handle() or a modified command_not_found_handle(), that does not need an unsuccessful PATH search to be triggered, would be useful and consistent. i found this old (Dec, 2009) discussion : http://gnu-bash.2382.n7.nabble.com/command-not-found-handle-not-called-if-comma

Told to report this bug here.

2010-01-08 Thread Frank J. R. Hanstick
ver (upgraded from a dual 800 MHz PowerPC G4) running MacOS 10.5.8. If there is anything more you need from me or something you would like me to try, feel free to contact me and I will do my best to accommodate your request. Frank J. R. Hanstick tro...@comcast.net

Colorizing PS4... needing PS4_AFTER ?

2009-11-22 Thread Frank Lin PIAT
Hello, I wish I could use PS4 to colorize debugging lines, like: PS4='\033[37m+ ' But I need to reset the color at the end of the line. I wish there were a similar variable to be able to reset the ansi code at the end of the line, like PS4_AFTER='\033[0m+' Do you know a hack to reset color at

pipe buffering

2005-11-07 Thread Frank Kujawski
command related. The specific command is tail httpd-*.logs | cut -c-80 While I presume this is an internal behavor to the CLI, I would liek to be able to turn it off. Frank ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org

"test -w aquota.user" gives different exit code after quotaon run

2005-08-19 Thread Frank Wang
Configuration Information [Automatically generated, do not change]: Machine: i386 OS: linux-gnu Compiler: i386-redhat-linux-gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i386-redhat-linux-gnu' -DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/sha

PIPESTATUS inconsistent behavior in 3.0

2005-08-10 Thread Frank Wang
Configuration Information [Automatically generated, do not change]: Machine: i386 OS: linux-gnu Compiler: i386-redhat-linux-gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' -DCONF_OSTYPE='linux-gnu ' -DCONF_MACHTYPE='i386-redhat-linux-gnu' -DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/sh