Re: [Resolved]Re: OT: M-S-$ Not Working
> On Sat, 6 Feb 2021 22:52:17 +0700, Maxim Nikulin > said: Maxim> P.S. Have you checked that it is possible to swap Ctrl and Caps in Maxim> wayland session? If not it is likely worth filing a bug. It seems Maxim> wayland will be default soon. Some Xkb stuff is already broken in Maxim> gnome (rather intentionally). My first experience with wayland was Maxim> that it took enough time to realize why I could not authenticate. Gdm Maxim> was using wayland by default and in password fields (hidden input!) Maxim> shift does not allow several capital letters in a row. I donʼt know about swapping Ctrl and Caps, but I have Caps -> Meta, Alt -> Ctrl, Ctrl -> Meta, Windows -> Super under Wayland, so I suspect you'll be ok. Robert
Re: [Resolved]Re: OT: M-S-$ Not Working
On Sat, 6 Feb 2021 22:52:17 +0700 Maxim Nikulin wrote: > On 06/02/2021 00:38, Bo Grimes wrote: > > > > I have no idea what 3rd level is, but before I ticked it I turned > > off my number lock, and C-S-$ worked! So I ticked it and it stopped > > working. So I unticked it and ticked Number keypad always enters > > digits, which is, of course, why I use Num Lock to begin with. > > Definitely "xev" is your friend if your want to realize actual effect > of such changes, along with "setxkbmap -query" (or "setxkbmap > -print") and "xkbcomp -xkb :0 -". > > 3rd level is intended to type some characters absent in regular > layout using a special modifier key. Personally I use 2 keyboard > layouts and compose key for some symbols that are not directly > available, so I do not need 3rd level as well. > > > With that ticked Emacs behaves as expected. I have always used Num > > Lock and never had that problems > > You could have a look into /usr/share/X11/xkb/rules/evdev.lst > /usr/share/X11/xkb/symbols/keypad /usr/share/X11/xkb/types/numpad > files. If I do not mistake, $ is mapped for keypad with > keypad:oss_wang option. Likely you could achieve what you want with > custom Xkb configuration. I have not tried such tricks however. The > most comprehensive guide on Xkb, I have seen, was in Russian. Its > English variant is incomplete, the author's site is down. > https://web.archive.org/web/20121108145326/http://pascal.tsu.ru/en/xkb/ > > X Keyboard Extension Protocol and library specifications could be > hard to read, XKB Configuration Guide hosted on x.org is too brief. > > P.S. Have you checked that it is possible to swap Ctrl and Caps in > wayland session? If not it is likely worth filing a bug. It seems > wayland will be default soon. Some Xkb stuff is already broken in > gnome (rather intentionally). My first experience with wayland was > that it took enough time to realize why I could not authenticate. Gdm > was using wayland by default and in password fields (hidden input!) > shift does not allow several capital letters in a row. > > Completely missed this. Thanks! I'm using Claws ATM because I'm still setting up Mu4e, with which I will capture this into a org file for later reference and notes. I would love to be able to help file a bug report, so I will *definitely* do this after I get my Emacs set-up fully on this new OS! Cheers, Bo Grimes
Re: [Resolved]Re: OT: M-S-$ Not Working
On 06/02/2021 00:38, Bo Grimes wrote: I have no idea what 3rd level is, but before I ticked it I turned off my number lock, and C-S-$ worked! So I ticked it and it stopped working. So I unticked it and ticked Number keypad always enters digits, which is, of course, why I use Num Lock to begin with. Definitely "xev" is your friend if your want to realize actual effect of such changes, along with "setxkbmap -query" (or "setxkbmap -print") and "xkbcomp -xkb :0 -". 3rd level is intended to type some characters absent in regular layout using a special modifier key. Personally I use 2 keyboard layouts and compose key for some symbols that are not directly available, so I do not need 3rd level as well. With that ticked Emacs behaves as expected. I have always used Num Lock and never had that problems You could have a look into /usr/share/X11/xkb/rules/evdev.lst /usr/share/X11/xkb/symbols/keypad /usr/share/X11/xkb/types/numpad files. If I do not mistake, $ is mapped for keypad with keypad:oss_wang option. Likely you could achieve what you want with custom Xkb configuration. I have not tried such tricks however. The most comprehensive guide on Xkb, I have seen, was in Russian. Its English variant is incomplete, the author's site is down. https://web.archive.org/web/20121108145326/http://pascal.tsu.ru/en/xkb/ X Keyboard Extension Protocol and library specifications could be hard to read, XKB Configuration Guide hosted on x.org is too brief. P.S. Have you checked that it is possible to swap Ctrl and Caps in wayland session? If not it is likely worth filing a bug. It seems wayland will be default soon. Some Xkb stuff is already broken in gnome (rather intentionally). My first experience with wayland was that it took enough time to realize why I could not authenticate. Gdm was using wayland by default and in password fields (hidden input!) shift does not allow several capital letters in a row.
[Resolved]Re: OT: M-S-$ Not Working
On Fri, 5 Feb 2021 21:40:25 +0700 Maxim Nikulin wrote: > On 05/02/2021 06:25, Bo Grimes wrote: > > > > OS: PopOS 20.10, DE: GNOME 3.38.2 WM: Mutter > > GNU Emacs 26.3 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.14) > > > > M-S-$ does not spellcheck word. > > Does C-h l view-lossage show something useful after an attempt to > perform spellcheck? Is there anything in the *Message* buffer? Thanks! I didn't know C-h l, and I never thought to check messages. Sorry, I'm a non-tech, learn-what-I-need-as-I-go-but-committed-to-FOSS guy. Unfortunately, messages doesn't show anything, and here's the output of C-h l, which I ran first as a marker, then typed a commonly misspelled word, did M-S-$, and then ran it again: C-h l [view-lossage] m [org-self-insert-command] i [org-self-insert-command] s [org-self-insert-command] p [org-self-insert-command] e [org-self-insert-command] l [org-self-insert-command] l [org-self-insert-command] C-h l [view-lossage] Nothing between the last two, which is when I did M-S-$ > > I could not suggest something in the case of wayland session, but if > it is X11 then attempt to acquire key grab should fail if another > application already set this shortcut. So you could try if e.g. > xbindkeys would report a conflict if such keystroke is added to its > config. I have never used it, but there is an interesting feature > XF86LogGrabInfo: > https://askubuntu.com/questions/406543/unable-to-set-a-shortcut-to-grab-screenshot-area > > Due to global shortcut emacs should lose focus for a moment and it > should be noticeable. I would also check if xev reports expected key > symbol. Just to be sure that $ is in its usual place yet. > So, that took me down a rabbit hole that led me nowhere in terms of understanding wayland, Xorg, or X11 configs, BUT, somewhere down there I got to thinking about how one of the first things I do on a new system is remap Ctrl to Caps Lock. I usually just do setxkbmap -layout us -option ctrl:nocaps, but in attempting to see if there was a problem there I was led to closely examine Tweeks Additional Layout Options, where I saw Shift Does Not Cancel Num Lock, choose 3rd lvl instead. I have no idea what 3rd level is, but before I ticked it I turned off my number lock, and C-S-$ worked! So I ticked it and it stopped working. So I unticked it and ticked Number keypad always enters digits, which is, of course, why I use Num Lock to begin with. With that ticked Emacs behaves as expected. I have always used Num Lock and never had that problems Wow! Thanks for taking the time to put me in the rabbit hole on an OT message!!! Frustrating, but less frustrating than a new distro or DM, and I learned some things! I am really grateful! Cheers, Bo Grimes
