Re: Why should `break' and `continue' in functions not break loops running outside of the function?

2021-11-02 Thread Dale R. Worley
Oğuz writes: >> It's a violation of scope. > > It's a violation of lexical scope, I'm asking why not implement > dynamic scope, what's wrong with it? Yes ... but the history of programming languages has been the history of learning that dynamic scoping is dangerous to program and lexical scoping

Re: Arbitrary command execution from test on a quoted string

2021-11-02 Thread Dale R. Worley
elettrino via Bug reports for the GNU Bourne Again SHell writes: > The following shows an example of bash testing a quoted string and as > a result executing a command embedded in the string. > > Here I used the command "id" to stand as an example of a command. The > output of id on this machine w

Re: bash support for XDG Base Directory spec (~/.config/bash/)

2021-11-02 Thread Dale R. Worley
Using XDG will have the complication that one normally sets environment variables like XDG_CONFIG_DIRS in ~/.bash_login. So I would add to the conversation, How much added value is there if XDG_CONFIG_DIRS is not used in practice? Dale

Re: Missing Backspace command in the readline

2021-11-02 Thread Chet Ramey
On 11/2/21 1:26 PM, Budi wrote: What is the Backspace code in the readline, i.e. .inputrc file (as the source come with explanation Ctrl-Backspace ( \b ) but not Backspace) ? Backspace is Control-H (^H, C-h). The default binding in emacs mode is backward-delete-char: $ bind -p | grep backward-

Missing Backspace command in the readline

2021-11-02 Thread Budi
What is the Backspace code in the readline, i.e. .inputrc file (as the source come with explanation Ctrl-Backspace ( \b ) but not Backspace) ?

Re: Assignment with colons *should* be tilde expanded in POSIX mode

2021-11-02 Thread Chet Ramey
On 11/1/21 6:37 PM, Anders Kaseorg wrote: As you know, POSIX requires tilde expansion following an an unquoted colon in an assignment [1]. A bug was reported [2] against bash 5.1-alpha that the tildes in $ echo foo=~:~ foo=~:~ should not be expanded in POSIX mode, because this is no

Re: bash support for XDG Base Directory spec (~/.config/bash/)

2021-11-02 Thread Siteshwar Vashisht
On Fri, May 7, 2021 at 11:48 AM Allison Karlitskaya < allison.karlitsk...@redhat.com> wrote: > hello, > > Please consider these two patches for inclusion in bash to support > storing shell initialisation files (profile, bashrc) in a subdirectory > of ~/.config/ as most programs do these days. > >

Re: some unknown bug, says : command not found

2021-11-02 Thread Alex fxmbsw7 Ratchev
i dont have "$var" <( sub ) i have $var <( sub ) else it makes sense On Tue, Nov 2, 2021, 13:42 Greg Wooledge wrote: > On Tue, Nov 02, 2021 at 04:52:24AM +0100, Alex fxmbsw7 Ratchev wrote: > > to answer around what was written, i dont have a cat alias > > > > but what mr andreas wrote seems much

Re: some unknown bug, says : command not found

2021-11-02 Thread Alex fxmbsw7 Ratchev
my fault i saw on the -x is an empty var indeed On Tue, Nov 2, 2021, 13:49 Alex fxmbsw7 Ratchev wrote: > i dont have "$var" <( sub ) i have $var <( sub ) > else it makes sense > > On Tue, Nov 2, 2021, 13:42 Greg Wooledge wrote: > >> On Tue, Nov 02, 2021 at 04:52:24AM +0100, Alex fxmbsw7 Ratchev

Re: some unknown bug, says : command not found

2021-11-02 Thread Alex fxmbsw7 Ratchev
but how why or to fix thers the code, thers the set -x parts ++ xblpp=. .. ++ '' /dev/fd/63 On Tue, Nov 2, 2021, 13:49 Alex fxmbsw7 Ratchev wrote: > i dont have "$var" <( sub ) i have $var <( sub ) > else it makes sense > > On Tue, Nov 2, 2021, 13:42 Greg Wooledge wrote: > >> On Tue, Nov 02, 2

Re: some unknown bug, says : command not found

2021-11-02 Thread Greg Wooledge
On Tue, Nov 02, 2021 at 04:52:24AM +0100, Alex fxmbsw7 Ratchev wrote: > to answer around what was written, i dont have a cat alias > > but what mr andreas wrote seems much similiar to what i do, process sub.. > ill check the vars carefully but i dont get it fully unicorn:~$ bash unicorn:~$ $xyz <

Re: some unknown bug, says : command not found

2021-11-02 Thread Alex fxmbsw7 Ratchev
bash xbl 0 exit // 22713s old , static means it exited 0 on old shell . xbl bash: : command not found 0 exit // 22775s old , static ( it didnt exit on that cmd not found ) On Tue, Nov 2, 2021, 09:19 Alex fxmbsw7 Ratchev wrote: > i completly dunno how to fix, it looks me like a bash bug due

Re: some unknown bug, says : command not found

2021-11-02 Thread Alex fxmbsw7 Ratchev
i completly dunno how to fix, it looks me like a bash bug due to unconsitency, .., i can try later on wsl2 on win11 debian, ..but ive had yet a lots of couple of inconsistency bugs like this, also to early startup symlink related i dont remember exactly anymore On Tue, Nov 2, 2021, 06:07 Alex fxmb