Re: [go-nuts] Why can't we use unicode? [Go2 Generics]

2018-09-13 Thread Wojciech S. Czarnecki
On Thu, 13 Sep 2018 12:16:10 -0700 (PDT) "'Bryan Mills' via golang-nuts" wrote: > Coincidentally, I contribute to a ChromeOS extension that adds XCompose > support,¹ > and I use a similar utility on Windows.² > (I'm not sure what's available on macOS.) https://scripts.sil.org/ukelele >

Re: [go-nuts] Why can't we use unicode? [Go2 Generics]

2018-09-13 Thread 'Bryan Mills' via golang-nuts
Coincidentally, I contribute to a ChromeOS extension that adds XCompose support,¹ and I use a similar utility on Windows.² (I'm not sure what's available on macOS.) ¹ https://github.com/bcmills/extra-keyboards-for-chrome-os/tree/custom-sequences ² https://github.com/samhocevar/wincompose On

Re: [go-nuts] Why can't we use unicode? [Go2 Generics]

2018-09-07 Thread Lucio
On Friday, 7 September 2018 18:39:38 UTC+2, Ian Cottrell wrote: > > The same thing works in any X system that supports compose, probably bound > to the Shift+AltGr > >> >> So, how do you apply an uppercase shift, when necessary, if you're already holding it down at the time? Or is Shift+AltGr

Re: [go-nuts] Why can't we use unicode? [Go2 Generics]

2018-09-07 Thread 'Ian Cottrell' via golang-nuts
The same thing works in any X system that supports compose, probably bound to the Shift+AltGr On Fri, Sep 7, 2018 at 12:29 PM roger peppe wrote: > In acme (and plan 9 generally), there's a nice set of mnemonic > abbreviations for unicode characters. > It's great, and I miss it in other

Re: [go-nuts] Why can't we use unicode? [Go2 Generics]

2018-09-07 Thread Jan Mercl
On Fri, Sep 7, 2018 at 6:29 PM roger peppe wrote: > In acme (and plan 9 generally), there's a nice set of mnemonic > abbreviations for unicode characters. > It's great, and I miss it in other environments. Alt-<< and Alt->> > work really well for « and » for example. > Here's the full list: >

Re: [go-nuts] Why can't we use unicode? [Go2 Generics]

2018-09-07 Thread roger peppe
In acme (and plan 9 generally), there's a nice set of mnemonic abbreviations for unicode characters. It's great, and I miss it in other environments. Alt-<< and Alt->> work really well for « and » for example. Here's the full list: https://github.com/9fans/plan9port/blob/master/lib/keyboard On 7

Re: [go-nuts] Why can't we use unicode? [Go2 Generics]

2018-09-07 Thread Michael Jones
I brought this up way back in the early days. There will be an old post. The fear is mental inertia and muscle memory -- a new-to-beginners character set would not "sell". An easy compromise is go vet: it can translate between '>=" to '≥' rather easily. On Fri, Sep 7, 2018 at 6:17 AM Larry

Re: [go-nuts] Why can't we use unicode? [Go2 Generics]

2018-09-07 Thread Larry Clapp
Need more shift keys! I'm pretty sure if I used them every day, I'd learn pretty quickly that « & » are from opt-\ and shift-opt-\, and ‹ & › are from shift-opt-3 & 4. Windows users ... are on their own. Find a use for the otherwise-poorly-used numeric keypad, maybe. (Sometimes I wish Macs

Re: [go-nuts] Why can't we use unicode? [Go2 Generics]

2018-09-06 Thread Mhd Shulhan
> > Why on earth keep on ascii? > > IPA: ʅ ʧ ʭ (0x285, 0x2a7, 0x2ad) > Latin-E: « » ¦ > Latin-A: Ħ ŧ Ŧ Ɏ > Latin-B: ǁ ǂ > Probably because its hard to type on most non ASCII keyboard. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To

Re: [go-nuts] Why can't we use unicode? [Go2 Generics]

2018-09-06 Thread 'Axel Wagner' via golang-nuts
And while we're at it, why "func", instead of the far simpler λ, or "type" instead of τ, or "include", instead of ι, "const" instead of κ and "war" instead of ω. We can do ρ instead of "range", φ instead of "for", ν is "new" and μ is "make", obviously. And while we're at it, let's also use ≥ and ≤