Hi Chet,
Thanks for the answers. The problem is now, that this behavior of the
bash creates some real problems outside, probably with a larger impact.
Before asking the kernel developers to change parts of linux kernel's
build system, I'd like to be sure whether bash-4.x's behavior is correct
or n
Chet Ramey wrote:
So what does the Solaris mbrtowc return in this case? The flow of that
particular section of code isn't that great (bash-4.0 is better), but it
seems to me that point can only increase. If mbrtowc returns -2, the
loop won't be entered at all.
I've checked it and looks to do
Jan Hnatek wrote:
> Hi Chet,
>
> unfortunately, there's additional problem with bash
> multibyte behavior, which is specific to sparc.
>
> When using bash patch level <49 on sparc in multibyte,
> pressing right arrow at the end of the line moves
> the cursor one character left.
>
> When using ba
Hi Chet,
unfortunately, there's additional problem with bash
multibyte behavior, which is specific to sparc.
When using bash patch level <49 on sparc in multibyte,
pressing right arrow at the end of the line moves
the cursor one character left.
When using bash patch level 49 on sparc in multiby
Chet Ramey writes:
> It's not a bug. Posix explicitly restricts environment variable names
> to consist of uppercase letters, lowercase letters, digits, and
> underscores.
POSIX only talks about their use in POSIX utilities. It does not say
anything about non-POSIX utilities and extensions (an
