Re: [STUMP] Possible bug with C-ae as a prefix-key

David Bjergaard <[email protected]>
Newsgroups gmane.comp.window-managers.stumpwm.devel
Message-ID <[email protected]>
Hi,

Do you press a modifier key to get ae? Are you trying to send a C-ae to
emacs? If that's the case, you'll need to type "C-ae ae", this is the
standard behavior for any prefix key (ie sending C-t to emacs requires
typing C-t t).  If you're setting the keycode like this:
> ,----
> | (set-prefix-key (kbd "C-ae"))
> `----
Its probably assuming that your prefix key is C-a, or C-a e (press
ctrl-a then e),  I don't know that stumpwm has support for this type of
key (it was written for the US 105 layout).  I'm not entirely sure what
it would take to support this entirely, probably adding the appropriate
keysym to key-code translator and handling the utf-8 string properly.  

If you want to open an issue on github I can look into this further,
otherwise just stick to "standard" keys for the prefix and everything
will work fine.

    Dave


Jón Gunnar Þorsteinsson <[email protected]> writes:

> Dear list.
>
> In my .stumpwmrc I have:
>
> ,----
> | (set-prefix-key (kbd "C-ae"))
> `----
>
> ae or æ is on:
>
> ,----
> | KeyPress event, serial 36, synthetic NO, window 0x1000001,
> |     root 0x8f, subw 0x0, time 1031519464, (294,845), root:(295,846),
> |     state 0x0, keycode 47 (keysym 0xe6, ae), same_screen YES,
> |     XLookupString gives 2 bytes: (c3 a6) "æ"
> |     XmbLookupString gives 2 bytes: (c3 a6) "æ"
> |     XFilterEvent returns: False
> `----
>
> This works fine, expect when I use C-a in other programs, such as
> Emacs. If I press C-a, nothing happens and Stump tells me:
>
> ,----
> | C-a not bound.
> `----
>
> My verison of Stump is: 0.9.8
>
> Is there any workaround so I can use C-ae as a prefix, or is this a bug?

_______________________________________________
Stumpwm-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/stumpwm-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.