What I find screwy is the way the caplock key gets interpreted. It whacks up menus, leads to easy (unwanted) select/replace of large blocks of text, and (understandably) breaks control-z to fix the later. Pharo is the only program I have seen to behave badly with the cap lock active.
Bill
-----Original Message-----
From:
[hidden email] [mailto:
[hidden email]] On Behalf Of Michael Rueger
Sent: Sunday, December 20, 2009 5:51 AM
To:
[hidden email]
Subject: Re: [Pharo-project] ^ on linux displayed as >
Bart Gauquie wrote:
> Hi,
>
> I apparently created :
>
http://code.google.com/p/pharo/issues/detail?id=1405 also; which is
> the same issue.
> Using latests 1.0 I still have the problem. If I press ^ and space, a
> [] block appears.
>
> On my Ubuntu, in a native texteditor, both work: If I press ^ twice,
> it appears correctly and if I press ^ followed by a space, the same happens.
on Linux key composition works in a pre-defined way by composing sequences. Or rather hardwired because of the way the VM delivers key events right now. Unfortunately that can be different from what is set for other applications.
That being said let me take a look if I can fix it anyways :-)
Michael
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Locked
