Re: Wildcard expansion can fail with nonprinting characters

2019-09-30 15:35:21 -0400, Chet Ramey: [...] > The $'\361' is a unicode combining > character, which ends up making the entire sequence of characters an > invalid wide character string in a bunch of different locales. [...] No, $'\u0361', the unicode character 0x361 (hex) is "COMBINING DOUBLE INVE

Re: Wildcard expansion can fail with nonprinting characters

$'\361' is a valid character in Latin-1, which is how it happened to arise in my case. Also, I tested with the C locale, which should be agnostic to character encodings, and got the same result. The general Unix philosophy, which in this case says "I'm not going to pass judgment on the weird

Expose READLINE_MARK patch?

Hi, I submitted a patch to savannah a few months ago that exposes READLINE_MARK in addition to the existing READLINE_POSITION. There has been no feedback on it so I'm wondering if that's not the normal workflow for submitting patches. Should they instead be posted to this list? Cheers, Len.

shebang-less script execution not resetting some options

A few of the recently-added shopt options aren't getting reset when running a shebang-less script, this should fix it up: --- a/builtins/shopt.def +++ b/builtins/shopt.def @@ -349,11 +349,16 @@ reset_shopt_options () inherit_errexit = 0; interactive_comments = 1; lastpipe_opt = 0; + loca

Re: Wildcard expansion can fail with nonprinting characters

On 9/27/19 7:52 PM, Geoff Kuenning wrote: > Version: > > GNU bash, version 4.4.23(1)-release (x86_64-suse-linux-gnu) > Copyright (C) 2016 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > > Behavior: > > If a pathname contains nonpri