-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sway: i3keys web - Supporting symbol key names starting with a capital letter. #39
Comments
I confirm. Quick fix is normalizing case in Line 101 in 99e368e
if strings.ToLower(symbol) == strings.ToLower(key.Key) There may be a better way but this seems to work. On a side note, key symbols are always capitalized in Line 52 in 99e368e
but /usr/include/X11/keysymdef.h , which is parsed to generate Line 4 in 99e368e
That should explain why XK_space has the problem but XK_Return does not.
|
Thank you for taking a look at this issue, and suggesting the fix!
Oh, I see. Thank you for providing this info. Now I understood why there are inconsistent symbol names in i3 config. It had been a mystery in my mind for a long term. |
I sent the PR #40! |
Hi, thanks for providing and maintaining this nice tool!
My environment
I am using sway on Fedora Linux 38.
I am using the i3keys on the current latest master branch 99e368e.
The issue summary
In sway, it's possible to define symbol keys as the name starting with a capital letter first such as Return, Space, Semicolon, Comma, Period, Slash. I can see these keys are not shown as occupied (red color) on the page by the
i3keys web
.I don't see the capital letter first names worked in i3 config except "Return". But it's nice if i3keys considers the capital letter first key names.
I am using this sway config.
https://github.com/junaruga/framework-laptop-config/blob/main/home/.config/sway/config
I was able to see the following
$mod+minus
was shown as occupied.Here is the actual screenshot. You can see these capital letter first keys are not shown as occupied (red).
The text was updated successfully, but these errors were encountered: