Jérôme Duval <korli@xxxxxxxxxxxxxxxx> wrote: > 2009/11/28 Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>: > > Jérôme Duval <korli@xxxxxxxxxxxxxxxx> wrote: > >> 2009/11/22 Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>: > >> Would it be OK to set MB_CUR_MAX to 4 in headers/posix/stdlib.h ? > >> Also gcc's limits.h defines MB_LEN_MAX to 1, although its value > > > would > >> be 16. Could we override this in our own limits.h ? > >> I tested locally with these changes and bash now behaves correctly > >> regarding the backspace bug described by Stefano. > > I think the MB_CUR_MAX macro should actually resolve to a function > > that > > takes the current encoding into account. Of course, it should > > default > > to UTF-8 for us (4 bytes), though. > > Where does our wide character implementation get its (default) > > encoding > > from? > I tried to use the glibc function, but it seems to default to 1. > #define MB_CUR_MAX (__ctype_get_mb_cur_max ()) Does it always stay 1, even if LANG is something like en.UTF-8? Bye, Axel.