On Sun, 2017-06-04 at 11:47 -0700, L A Walsh wrote:
> dualbus wrote:
> >
> > I hadn't realized that bash already supports Unicode in function names!
> > FWIW:
> >
> > bash-4.4$
> > Lēv=?
> > Φ=0.618033988749894848
> >
> >
> > With this terrible patch:
> >
> > dualbus@debian:~/src/gnu/
On 05/06/2560 15:52, George wrote:
> there's not a reliable mechanism in place to run a script in a locale
> whose character encoding doesn't match that of the script
>From my experience running such scripts is no problem, but correct
rendering it might depend on the client/editor.
On 06/04/2017 11:39 AM, Nicola Spanti wrote:
> Hi.
>
> I used that:
> cppcheck --verbose --quiet --enable=all --force --language=c --std=c89 .
>
> I fixed some errors that were reported by cppcheck. I published that on
> GitLab.com.
> https://gitlab.com/RyDroid/bash
>
> The git remote is: https:
On Sun, Jun 04, 2017 at 09:20:45AM +0700, Peter & Kelly Passchier wrote:
> On 04/06/2560 04:48, L A Walsh wrote:
> >> Greg Wooledge wrote:
> >>> Here is a demonstration of the cost of what you are proposing. In my
> >>> mail user agent, your variable shows up as L??v.
> >>>
> >>> Source code with
On Mon, Jun 05, 2017 at 04:52:19AM -0400, George wrote:
[...]
> To hazard a guess: Each call to legal_identifier() and assignment() in
> the patched code requires copying the parameter and translating it to
> a wide-character string (with no provision for skipping the added work
> as a build option
On Mon, 2017-06-05 at 15:59 +0700, Peter & Kelly Passchier wrote:
> On 05/06/2560 15:52, George wrote:
> >
> > there's not a reliable mechanism in place to run a script in a locale
> > whose character encoding doesn't match that of the script
> From my experience running such scripts is no problem
George wrote:
On Mon, 2017-06-05 at 15:59 +0700, Peter & Kelly Passchier wrote:
On 05/06/2560 15:52, George wrote:
there's not a reliable mechanism in place to run a script in a locale
whose character encoding doesn't match that of the script
From my experience running such scri
On 06/06/2560 05:39, George wrote:
> So if you had "Pokémon" as an identifier in a Latin-1-encoded script (byte
> value 0xE9 between the "k" and "m") and then tried running that script in a
> UTF-8 locale, that byte sequence (0xE9 0x6D) would actually be invalid in
> UTF-8, so Eduardo's patch wou
