Re: Multiline editing breaks if the previous output doesn't end in newline

2022-10-28 Thread Albert Vaca Cintora
On Sat, Oct 29, 2022 at 7:28 AM Koichi Murase wrote: > > 2022年10月28日(金) 21:24 Albert Vaca Cintora : > > Description: > > When there's leftover output before the prompt (ie: when the > > previous command output doesn't end in a new line), editing a > > multi-line command from history doesn'

Re: bash "extglob" needs to upgrade at least like zsh "kshglob"

2022-10-28 Thread Martin D Kealey
This seems like a good reason to simply translate extglobs into regexes, which should run in linear time, rather than put effort into building and debugging a parallel implementation. -Martin PS: While we're about it, can we please fix the expansion of « a/*/b/c/d/* » so it only calls readdir on

Re: Multiline editing breaks if the previous output doesn't end in newline

2022-10-28 Thread Koichi Murase
2022年10月28日(金) 21:24 Albert Vaca Cintora : > Description: > When there's leftover output before the prompt (ie: when the > previous command output doesn't end in a new line), editing a > multi-line command from history doesn't correctly display what you > edit. > > [...] > Option A:

Re: Function declarations produce no trace nor trigger debug trap while having side effects

2022-10-28 Thread Oğuz
28 Ekim 2022 Cuma tarihinde Erik Adelbert yazdı: > > 1 there is an error > 2 the debug TRAP is not invoked before the function definition > 3 the function definition is required to return 0 if successful > 4 the debug TRAP is invoked after the successful function definition > > Thi

Re: Function declarations produce no trace nor trigger debug trap while having side effects

2022-10-28 Thread Erik Adelbert
Hello Chet and other bash maintainers, Thanks for your time. > On 27 Oct 2022, at 23:26, Chet Ramey wrote: > > we believe the current semantic to be at least unclear and would like to see > either: >> 0 the DEBUG trap called _before_ any function declaration (preferred) > > While calling the

Re: bash "extglob" needs to upgrade at least like zsh "kshglob"

2022-10-28 Thread Greg Wooledge
On Fri, Oct 28, 2022 at 03:44:34PM +0900, Hyunho Cho wrote: > # this is just for testing purposes. > $ foo=$( gcc -v --help 2> /dev/null | sed -En 's/^\s*(-[^ ]+).*/\1/p' ) The last time this issue was reported, we mentioned that "gcc --help" is not a standard document that appears the same on eve

Subsequent Here Doc/String Never Evaluated in Process Substitution

2022-10-28 Thread admin
Thank you for the awesome shell. I noticed the following after upgrading from 5.1.16-3 to 5.2.2-2 on Fedora. It actually resulted in a minor amount of data loss. #!/usr/bin/env -S bash -- mapfile -t < <( cat <<- EOF ;FFMETADATA1 EOF while read -r ; do

Multiline editing breaks if the previous output doesn't end in newline

2022-10-28 Thread Albert Vaca Cintora
Machine: All archs OS: All OSes Bash Version: All versions since I have memory Description: When there's leftover output before the prompt (ie: when the previous command output doesn't end in a new line), editing a multi-line command from history doesn't correctly display what you edit. R