Christian Gollwitzer :
> Am 28.11.17 um 20:24 schrieb wxjmfa...@gmail.com:
>> 00FF LETTRE MINUSCULE LATINE Y TRÉMA
>
> WTF is this? The character is correctly called
> "LATIN SMALL LETTER Y WITH DIAERESIS". There is no non-ASCII character
> in this description. Of course, if I
Am 28.11.17 um 20:24 schrieb wxjmfa...@gmail.com:
Le mardi 28 novembre 2017 04:44:51 UTC+1, Rustom Mody a écrit :
...
Unicode codepoint names are (evidently) ALLCAPS-ASCII
Are you sure ? ;-)
; Standard Unicode 10.0.0 ou
; Norme internationale ISO/CEI 10646:2017
...
00FFLETTRE
On Wed, Nov 29, 2017 at 3:44 PM, Gregory Ewing
wrote:
> Chris Angelico wrote:
>>
>> Heh, you mean the term "Windows key"? It's not appropriate on
>> keyboards that don't have an actual Windows logo on it. There are
>> other names for it, but I figured the easiest way
Chris Angelico wrote:
Heh, you mean the term "Windows key"? It's not appropriate on
keyboards that don't have an actual Windows logo on it. There are
other names for it, but I figured the easiest way was to describe its
location :D
That doesn't work for all keyboards, though. The one I'm using
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,
On 28/11/2017 08:41, Paul Moore wrote:
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
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
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
On Mon, Nov 27, 2017 at 8:09 PM, Alexandre Brault wrote:
> A quick Google search turned up WinCompose. It defaults to Right-Alt for
> its compose key, but that's configurable
>
> On 2017-11-27 02:05 PM, Paul Moore wrote:
>> On 27 November 2017 at 18:13, Skip Montanaro
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
A quick Google search turned up WinCompose. It defaults to Right-Alt for
its compose key, but that's configurable
On 2017-11-27 02:05 PM, 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
>>>
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
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
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
> 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
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-\)
> 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
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
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
> 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
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
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-\)
> 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
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
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
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
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
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
On 11/24/17 12:35 PM, Skip Montanaro wrote:
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
> 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
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
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
> 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
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
35 matches
Mail list logo