Re: Missing semicolon tolerated after double-bracket [[ ]] expression

2025-09-15 Thread Andreas Schwab
On Sep 15 2025, Chet Ramey wrote: > On 9/13/25 10:55 AM, Lawrence Velázquez wrote: > >> Yeah, I misunderstood how locale_setblanks [1] works. Its function >> comment is: >> Set every character in the character class to be a >> shell break character for the lexical analyzer when the >>

Re: trap and BASH_COMMAND

2025-09-15 Thread Chet Ramey
On 9/13/25 5:45 AM, Mike Jonkmans wrote: Thanks for your answers. On Fri, Sep 12, 2025 at 04:31:07PM -0400, Chet Ramey wrote: On 9/11/25 5:02 PM, Mike Jonkmans wrote: The below script echoes (when saved to bash_command.bash): Trace: 1: bash_command.bash:29 onerror () 2: bash_command.ba

Re: [PATCH] ansic_quote: zero mbstate when needed

2025-09-15 Thread Chet Ramey
On 9/14/25 1:50 AM, Grisha Levit wrote: ansic_quote calls mbrtowc with a NULL parser state argument. This uses a static anonymous shift state that ends up in an undefined state after an invalid sequence. AFAICT most libcs handle UTF-8 conversions with the static state just fine, but on Android [1

Re: Missing semicolon tolerated after double-bracket [[ ]] expression

2025-09-15 Thread Oğuz
On Mon, Sep 15, 2025 at 7:34 PM Lawrence Velázquez wrote: > Of the shells I have at hand, running under a UTF-8 locale on macOS, > only yash delimits on anything other than space and tab. FWIW the original ksh88 on both Solaris and Unixware delimit tokens on all members of the blank class defined

Re: Missing semicolon tolerated after double-bracket [[ ]] expression

2025-09-15 Thread Collin Funk
Andreas Schwab writes: > On Sep 15 2025, Chet Ramey wrote: > >> On 9/13/25 10:55 AM, Lawrence Velázquez wrote: >> >>> Yeah, I misunderstood how locale_setblanks [1] works. Its function >>> comment is: >>> Set every character in the character class to be a >>> shell break character for t

Re: Missing semicolon tolerated after double-bracket [[ ]] expression

2025-09-15 Thread Greg Wooledge
On Mon, Sep 15, 2025 at 12:32:05 -0400, Lawrence Velázquez wrote: > Of the shells I have at hand, running under a UTF-8 locale on macOS, > only yash delimits on anything other than space and tab. (I tested > the twenty-five Unicode whitespace characters [*]. Eighteen of > them are s in my locale,

Re: Missing semicolon tolerated after double-bracket [[ ]] expression

2025-09-15 Thread Chet Ramey
On 9/14/25 3:08 PM, Robert Elz wrote: There is really nothing in the standard I can find which is explicit about how locales affect parsing of programs using any of the languages it defines (awk, bc, sed, sh ...) - and I would certainly hesitate to jump to the conclusion that the locale settings

Re: Missing semicolon tolerated after double-bracket [[ ]] expression

2025-09-15 Thread Lawrence Velázquez
On Sun, Sep 14, 2025, at 3:21 PM, Robert Elz wrote: > Date:Sun, 14 Sep 2025 13:23:06 -0400 > From:=?UTF-8?Q?Lawrence_Vel=C3=A1zquez?= > Message-ID: > > | yash takes this very seriously. > > And is very much the outlier - I couldn't find any other shell which > reports o

Re: Missing semicolon tolerated after double-bracket [[ ]] expression

2025-09-15 Thread Chet Ramey
On 9/15/25 10:46 AM, Robert Elz wrote: If it was intended to mean "parsing the script" it would certainly say so. Doesn't the fact that the discussion of token recognition includes the references to s imply this? -- ``The lyf so short, the craft so long to lerne.'' - Chaucer

Re: more readline signal issue examples

2025-09-15 Thread Chet Ramey
On 9/5/25 8:21 PM, Grisha Levit wrote: On Thu, Sep 4, 2025 at 12:05 PM Chet Ramey wrote: Well, definitely a few. Thanks for the report. If you find other places where signals cause data to be freed, please report them as well. Sure, a couple variations on the recent reports: Thanks for the

Re: Missing semicolon tolerated after double-bracket [[ ]] expression

2025-09-15 Thread Robert Elz
Date:Mon, 15 Sep 2025 09:51:01 -0400 From:Chet Ramey Message-ID: <584c7249-b6a5-430e-9ce2-46e4a5091...@case.edu> | At least for sh -- I didn't look at the other utilities -- the standard is | fairly explicit that characters delimit tokens, and is | locale-spe

Re: Missing semicolon tolerated after double-bracket [[ ]] expression

2025-09-15 Thread Greg Wooledge
On Mon, Sep 15, 2025 at 09:51:01 -0400, Chet Ramey wrote: > At least for sh -- I didn't look at the other utilities -- the standard is > fairly explicit that characters delimit tokens, and is > locale-specific. I would respectfully ask that this interpretation, should you choose to abide by it,

Re: Missing semicolon tolerated after double-bracket [[ ]] expression

2025-09-15 Thread Chet Ramey
On 9/13/25 10:55 AM, Lawrence Velázquez wrote: Yeah, I misunderstood how locale_setblanks [1] works. Its function comment is: Set every character in the character class to be a shell break character for the lexical analyzer when the locale changes. But it seems to onl

Re: Missing semicolon tolerated after double-bracket [[ ]] expression

2025-09-15 Thread Chet Ramey
On 9/13/25 6:12 AM, Duncan Roe via Bug reports for the GNU Bourne Again SHell wrote: I believe bash mostly tokenizes on characters. Is U+00A0 considered a in your locale? -- vq It certainly *renders* as a space. Other than that, I'm not sure I understand your question. https://pubs.open

A problem with the read command

2025-09-15 Thread pourko--- via Bug reports for the GNU Bourne Again SHell
Greetings, you almighty problem-solvers! I'll illustrate my problem with a couple of simple examples. Let's set aside for the moment the reason for doing something like this: fun1 () { local tty   if [ -t 1 ] ;then tty=1; elif [ -t 2 ] ;then tty=2; elif [ -t 0 ] ;then tty=0; else return 1; fi