w2022年11月15日(火) 5:31 Chet Ramey :
> On 11/14/22 11:40 AM, Koichi Murase wrote:
> > 2022年11月15日(火) 0:22 Chet Ramey :
> >> On 8/11/22 5:56 PM, Koichi Murase wrote:
> >>> Can we also change the behavior of TERM in a similar way with option
> >>> 4? Currently, a temporal change of TERM clears
On 11/14/22 11:40 AM, Koichi Murase wrote:
2022年11月15日(火) 0:22 Chet Ramey :
On 8/11/22 5:56 PM, Koichi Murase wrote:
Can we also change the behavior of TERM in a similar way with option
4? Currently, a temporal change of TERM clears keybindings of some
keys (home, end, right, left, etc.) even
On 8/11/22 5:56 PM, Koichi Murase wrote:
Can we also change the behavior of TERM in a similar way with option
4? Currently, a temporal change of TERM clears keybindings of some
keys (home, end, right, left, etc.) even when the temporal change does
not survive across multiple calls of readline:
2022年11月15日(火) 0:22 Chet Ramey :
> On 8/11/22 5:56 PM, Koichi Murase wrote:
> > Can we also change the behavior of TERM in a similar way with option
> > 4? Currently, a temporal change of TERM clears keybindings of some
> > keys (home, end, right, left, etc.) even when the temporal change does
>
On 8/11/22 5:56 PM, Koichi Murase wrote:
I agree with option 4. Thank you for all your explanations.
--
Can we also change the behavior of TERM in a similar way with option
4?
I'll look at that for the next version.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
2022年8月12日(金) 4:22 Chet Ramey :
> >> Often enough to make a difference?
> >
> > My `bind -x' functions use `LC_ALL=' and `LC_CTYPE=C' for every
> > keystroke, for example, in combination with `builtin read'. They also
> > use `LC_ALL=' for other purposes for mostly every keystroke. Some vi
> >
On 8/10/22 10:59 PM, Koichi Murase wrote:
2022年8月10日(水) 23:21 Chet Ramey :
Does it mean custom values of these readline variables will be lost
every time LANG or LC_{CTYPE,ALL} is changed even if a user or program
intentionally sets them up?
It means those settings will now mirror the locale.
2022年8月10日(水) 23:21 Chet Ramey :
> > Does it mean custom values of these readline variables will be lost
> > every time LANG or LC_{CTYPE,ALL} is changed even if a user or program
> > intentionally sets them up?
>
> It means those settings will now mirror the locale.
>
> > We often temporarily
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
On 8/9/22 4:50 PM, Koichi Murase wrote:
> 2022年8月10日(水) 2:07 Alan Coopersmith :
Thanks for the report. The eight-bit settings are auto-set once, when
readline is first called, but I'll see if it makes sense to change them
on every call.
>>>
>>> It's fairly easy. I'll make the change
2022年8月10日(水) 2:07 Alan Coopersmith :
> >> Thanks for the report. The eight-bit settings are auto-set once, when
> >> readline is first called, but I'll see if it makes sense to change them
> >> on every call.
> >
> > It's fairly easy. I'll make the change for the next devel branch push and
> >
On 8/9/22 08:15, Chet Ramey wrote:
On 8/9/22 10:45 AM, Chet Ramey wrote:
On 8/8/22 5:48 PM, Alan Coopersmith wrote:
One of our users complained that bash-5.1 on Solaris 11.4, when started
with LANG=C does not allow Unicode input after changing LANG to a UTF-8
locale until bash is restarted.
On 8/9/22 10:45 AM, Chet Ramey wrote:
> On 8/8/22 5:48 PM, Alan Coopersmith wrote:
>> One of our users complained that bash-5.1 on Solaris 11.4, when started
>> with LANG=C does not allow Unicode input after changing LANG to a UTF-8
>> locale until bash is restarted.
>
> Thanks for the report.
On 8/8/22 5:48 PM, Alan Coopersmith wrote:
> One of our users complained that bash-5.1 on Solaris 11.4, when started
> with LANG=C does not allow Unicode input after changing LANG to a UTF-8
> locale until bash is restarted.
Thanks for the report. The eight-bit settings are auto-set once, when
One of our users complained that bash-5.1 on Solaris 11.4, when started
with LANG=C does not allow Unicode input after changing LANG to a UTF-8
locale until bash is restarted.
I've confirmed this is the default behavior, but can be overridden by
manually changing the readline output-meta flag
One of our users complained that bash-5.1 on Solaris 11.4, when started
with LANG=C does not allow Unicode input after changing LANG to a UTF-8
locale until bash is restarted.
I've confirmed this is the default behavior, but can be overridden by
manually changing the readline output-meta flag
16 matches
Mail list logo