@gar, what do you get for
$ setxkbmap -print | grep xkb_geometry
xkb_geometry { include "pc(pc105)" }; # my VM
On Tuesday, March 8, 2022 at 8:42:16 PM UTC-5 [email protected] wrote:
> Without ever learning the cause of this problem, it could be finessed by
> just ignoring that exact keystroke, like this:
>
> def masterKeyHandler(self, event):
> """The master key handler for almost all key bindings."""
> trace = 'keys' in g.app.debug
> c, k = self.c, self
> # Setup...
> if trace:
> g.trace(repr(k.state.kind), repr(event.char), repr(event.stroke))
> *if event.char == 'ៀ\udc53': return*
>
> This works on my Debian machine. It's hard for me to believe that anyone
> is going to type that exact sequence on purpose. OTOH, what if on some
> other installation and OS version some other spurious key gets emitted?
> Maybe there should be a new setting
>
> @string ignored-keys = *'ៀ\udc53 *# I can't delete that leading
> apostrophe; this sequence even confuses the browser editor.
>
> Better to find the root cause if possible, but this hack would at least
> get Leo usable again for the afflicted.
> On Tuesday, March 8, 2022 at 8:14:45 PM UTC-5 [email protected] wrote:
>
>> Running with --trace=keys gives this output for SHIFT-Windows, which
>> doesn't help me a lot -
>>
>> masterKeyHandler None 'ៀ\udc53' <KeyStroke: 'Shift+ៀ\udc53'>
>> selfInsertCommand ch 'ៀ\udc53'
>>
>>
>> On Tuesday, March 8, 2022 at 6:22:25 PM UTC-5 [email protected] wrote:
>>
>>> The hex codes for this string are 20 E1 9F 80 3F, for what that's
>>> worth. And yes, it does seem that "20" is part of it and not an accidental
>>> addition during copying.
>>>
>>> On Tuesday, March 8, 2022 at 6:12:58 PM UTC-5 [email protected] wrote:
>>>
>>>> Bingo! I installed a stock KUbuntu from an iso file I just downloaded.
>>>> The keyboard is standard for us-en. I installed pip then Leo. When I
>>>> hit
>>>> the Windows key I get that same symbol group inserted into the body.
>>>>
>>>> I didn't expect that because that key is used by the OS GUI to bring up
>>>> the system's program menu, and I would have had thought that the key would
>>>> never get through to Leo.
>>>>
>>>> I also get it for SHIFT-Windows. I don't get it for ALT or CTRL, or
>>>> their SHIFT versions. I also get it with SHIFT=Windows on Ubuntu and
>>>> Debian
>>>> but not with just the Windows key. Here's what I get on the latter two:
>>>>
>>>> ៀ?
>>>>
>>>> Well, now maybe we can make some progress! Except I don't know
>>>> anything about Leo's key handling. @Edward, can you install KUbuntu or
>>>> Debian and track this problem down?
>>>> On Tuesday, March 8, 2022 at 2:05:49 PM UTC-5 [email protected] wrote:
>>>>
>>>>> On Tuesday, March 8, 2022 at 1:24:49 PM UTC-5 gar wrote:
>>>>>
>>>>>>
>>>>>> $ setxkbmap -print | grep xkb_symbols
>>>>>> xkb_symbols { include
>>>>>> "pc+us+ru:2+inet(evdev)+capslock(grouplock)" };
>>>>>>
>>>>>
>>>>> My current Mint VM:
>>>>>
>>>>> tom@tom-VirtualBox:~$ setxkbmap -print | grep xkb_symbols
>>>>> xkb_symbols { include
>>>>> "pc+us+inet(evdev)+terminate(ctrl_alt_bksp)" };
>>>>>
>>>>> I wonder if the "+ru" has anything to do with it?
>>>>>
>>>>> Your symbols indicate that you have another keyboard layout,
>>>>> presumably ":1". Is that different? Can you switch to it and see if you
>>>>> still have the problem?
>>>>>
>>>>
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/leo-editor/d84abd9e-32ff-49c4-8035-5cae07aa9387n%40googlegroups.com.
