On 8/10/22 10:21 AM, Chet Ramey wrote: > I'm not going to make this much of a change at this point in the release > process. I was willing to make the change I did because the changed > behavior is a superset of the previous behavior. > > So, assuming we say that the scenario Alan outlined is reasonable (it is), > it looks like there are four alternatives: > > 1. Do nothing; maintain the bash-5.1 behavior and force the change to the > user. > > 2. Leave the new function in place; automatically adjust to locale > changes. > > 3. Push it off to the application: introduce a new readline API that > applications can call when locale variables change. This is very cheap. > > 4. Push it onto readline: instead of checking the locale and making the > eight-bit variables mirror it on each call, make readline check for > locale changes (well, LC_CTYPE) and reset the eight-bit variables only > if the current value doesn't match the value from the last call. > > The last option is about as much of a change as I'm willing to make at > this point.
There is a fifth option: 5. Make the locale-aware behavior dependent on a new readline option, which would be enabled by default. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/