On 2017-11-24 17:41, Skip Montanaro wrote:
> Perhaps for my next computer I should choose a
> non-ASCII keyboard option when configuring it.
>
> Skip
>
I'm quite fond of the US international keyboard layout. It lets you type
most Latin-lettered languages with relative ease (including, obviously,
On 27 November 2017 at 19:05, Paul Moore wrote:
> On 27 November 2017 at 18:13, Skip Montanaro wrote:
>>> If you have a Windows key, you can assign it to be
>>> the Compose key.
>>
>> Would this be true on a machine running Windows? My work environment
>> has me developing on Linux, with a Window
On Monday, November 27, 2017 at 10:49:35 PM UTC+5:30, Skip Montanaro wrote:
> > I strongly suspect that any recent emacs will have M-x insert-char
> > (earlier it was called ucs-insert) default bound C-x 8 RET (yeah thats
> > clunky)
> > which will accept at the minibuffer input
>
> I tried C-x 8
On Monday, November 27, 2017 at 8:07:47 PM UTC+5:30, Chris Angelico wrote:
> On Tue, Nov 28, 2017 at 1:25 AM, Rustom Mody wrote:
> > You could go one step more sophisticated and use TeX-input method
> > (C-x RET C-\)
> > After which \'e will collapse as ÄC
> > â £Yeah ok but how the ^)*^$# am I to
On Friday, November 24, 2017 at 10:11:24 PM UTC+5:30, Skip Montanaro wrote:
> > Because if I already can't understand the words, it will be more useful
> > to me to be able to type them reliably at a keyboard, for replication,
> > search, discussion with others about the code, etc.
>
> I am probabl
On 27 November 2017 at 18:13, Skip Montanaro wrote:
>> If you have a Windows key, you can assign it to be
>> the Compose key.
>
> Would this be true on a machine running Windows? My work environment
> has me developing on Linux, with a Windows desktop. It's not clear to
> me that any sort of xmodm
On Tue, Nov 28, 2017 at 5:13 AM, Skip Montanaro
wrote:
>> If you have a Windows key, you can assign it to be
>> the Compose key.
>
> Would this be true on a machine running Windows? My work environment
> has me developing on Linux, with a Windows desktop. It's not clear to
> me that any sort of xm
> I strongly suspect that any recent emacs will have M-x insert-char
> (earlier it was called ucs-insert) default bound C-x 8 RET (yeah thats
clunky)
> which will accept at the minibuffer input
I tried C-x 8 e acute TAB
and was prompted with "E-acute". I don't know why it would have capitalized t
On Tue, Nov 28, 2017 at 1:55 AM, Rustom Mody wrote:
> On Monday, November 27, 2017 at 8:07:47 PM UTC+5:30, Chris Angelico wrote:
>> On Tue, Nov 28, 2017 at 1:25 AM, Rustom Mody wrote:
>> > You could go one step more sophisticated and use TeX-input method
>> > (C-x RET C-\)
>> > After which \'e wil
> If you have a Windows key, you can assign it to be
> the Compose key.
Would this be true on a machine running Windows? My work environment has me
developing on Linux, with a Windows desktop. It's not clear to me that any sort
of xmodmap shennanigans would work. Won't Windows itself always gobbl
On Tue, Nov 28, 2017 at 1:25 AM, Rustom Mody wrote:
> You could go one step more sophisticated and use TeX-input method
> (C-x RET C-\)
> After which \'e will collapse as ÄC
> â £Yeah ok but how the ^)*^$# am I to remember the mantra \'e?!â Ø you may
ask
> Trueâ | So as you rightly do,
> - pick it
On 27 November 2017 at 18:13, Skip Montanaro wrote:
>> If you have a Windows key, you can assign it to be
>> the Compose key.
>
> Would this be true on a machine running Windows? My work environment
> has me developing on Linux, with a Windows desktop. It's not clear to
> me that any sort of xmodm
> If you have a Windows key, you can assign it to be
> the Compose key.
Would this be true on a machine running Windows? My work environment
has me developing on Linux, with a Windows desktop. It's not clear to
me that any sort of xmodmap shennanigans would work. Won't Windows
itself always gobble
On Tue, Nov 28, 2017 at 5:13 AM, Skip Montanaro
wrote:
>> If you have a Windows key, you can assign it to be
>> the Compose key.
>
> Would this be true on a machine running Windows? My work environment
> has me developing on Linux, with a Windows desktop. It's not clear to
> me that any sort of xm
On Tue, Nov 28, 2017 at 1:55 AM, Rustom Mody wrote:
> On Monday, November 27, 2017 at 8:07:47 PM UTC+5:30, Chris Angelico wrote:
>> On Tue, Nov 28, 2017 at 1:25 AM, Rustom Mody wrote:
>> > You could go one step more sophisticated and use TeX-input method
>> > (C-x RET C-\)
>> > After which \'e wil
> I strongly suspect that any recent emacs will have M-x insert-char
> (earlier it was called ucs-insert) default bound C-x 8 RET (yeah thats clunky)
> which will accept at the minibuffer input
I tried C-x 8 e acute TAB
and was prompted with "E-acute". I don't know why it would have
capitalized t
On Monday, November 27, 2017 at 8:07:47 PM UTC+5:30, Chris Angelico wrote:
> On Tue, Nov 28, 2017 at 1:25 AM, Rustom Mody wrote:
> > You could go one step more sophisticated and use TeX-input method
> > (C-x RET C-\)
> > After which \'e will collapse as é
> > “Yeah ok but how the ^)*^$# am I to rem
On Tue, Nov 28, 2017 at 1:25 AM, Rustom Mody wrote:
> You could go one step more sophisticated and use TeX-input method
> (C-x RET C-\)
> After which \'e will collapse as é
> “Yeah ok but how the ^)*^$# am I to remember the mantra \'e?!” you may ask
> True… So as you rightly do,
> - pick it up fro
On Friday, November 24, 2017 at 10:11:24 PM UTC+5:30, Skip Montanaro wrote:
> > Because if I already can't understand the words, it will be more useful
> > to me to be able to type them reliably at a keyboard, for replication,
> > search, discussion with others about the code, etc.
>
> I am probab
On Friday, November 24, 2017 at 10:52:47 PM UTC+5:30, Rick Johnson wrote:
> Furthermore, if we are to march headlong onto the glorious
> battlefields of diversity and equality…
Obligatory viewing for those who underappreciate diversity, equality and such
https://youtu.be/Zh3Yz3PiXZw
[My old coll
Thank you Rick for well thought out argument.
On Nov 24, 2017 12:44, "Rick Johnson" wrote:
> On Thursday, November 23, 2017 at 9:57:12 PM UTC-6, Ben Finney wrote:
> [...]
> > This is a necessary consequence of increasing the diversity
> > of people able to program in Python: people will expres
> I find it it interesting that the primary reason to want to limit the
> character set to ASCII is people thinking that it would make it hard for
> *them* to read/use the code, but no thought about how much harder it makes
> it on the original author/team to write code that is easily understood by
On Thursday, November 23, 2017 at 9:57:12 PM UTC-6, Ben Finney wrote:
[...]
> This is a necessary consequence of increasing the diversity
> of people able to program in Python: people will express
> ideas originating in their own language, in Python code.
> For that diversity to increase, we Englis
On 11/24/17 11:41 AM, Skip Montanaro wrote:
Because if I already can't understand the words, it will be more useful
to me to be able to type them reliably at a keyboard, for replication,
search, discussion with others about the code, etc.
I am probably not alone in my Americo-centric world where
> Because if I already can't understand the words, it will be more useful
> to me to be able to type them reliably at a keyboard, for replication,
> search, discussion with others about the code, etc.
I am probably not alone in my Americo-centric world where I can't even
easily type accented Latin
On 24/11/17 05:45, Andrew Z wrote:
> I have hard time seeing the benefits of this "necessity" , just
> unreasonable overcomplications for the name of "diversity".
What complications?
--
https://mail.python.org/mailman/listinfo/python-list
I have hard time seeing the benefits of this "necessity" , just
unreasonable overcomplications for the name of "diversity".
On Nov 23, 2017 22:57, "Ben Finney" wrote:
> Ian Kelly writes:
>
> > On Thu, Nov 23, 2017 at 1:04 PM, Karsten Hilbert
> > wrote:
> > > Using function arguments writte
Ian Kelly writes:
> On Thu, Nov 23, 2017 at 1:04 PM, Karsten Hilbert
> wrote:
> > Using function arguments written in Thai script ?
> >
> > Understanding, let alone being able to read, code written in Arabic
> > ?
>
> People are going to write code in Arabic whether you like it or not,
> because
28 matches
Mail list logo
