Symbols of '>' and '<'

[VictorLemosR]

It's a simple question, I'm remapping all my punctuations buttons, but couldn't find the '>' and '<' symbols. I've looked on keys, but still no luck

[rszyma]

This is similar to #459

On US keyboard you can get < by using S-, output chord

I feel like it's quite common for new kanata users to try using shifted characters directly, so documentation on this should probably be improved. @VictorLemosR If you have any idea what could be changed in config doc feel free to suggest.

[jtroo]

The feature you might be looking for might also be this:

https://github.com/jtroo/kanata/blob/main/docs/config.adoc#non-us-keyboards

Definite agree that suggestions for improving documentation are much appreciated!

As another note, I do not plan to add or allow builtin shortcuts for symbols/characters that are reached via modifiers like shift or altgr. These outputs vary by locale/keyboard layout, so it seems quite difficult to give a consistent experience.

[VictorLemosR]

@jtroo thank your for response. Actually, my case is kinda the opposite, I want to stay on us-layout and type accented characters.

My previous solution (before kanata) was to change on windows to international us layout, which almost works perfectly fine, but I have to double press ' or " to make them appear.

Now, on us layout, my aim is to make some macro for all the accented letter

I've discovered that if I press alt+0231 on keypad, for example, I get 'ç'.
I'd say I'm close, but any help is greatly appreciated:
'c (macro A-kp0-kp2-kp3-kp1)
'c (macro A-(kp0 kp2 kp3 kp1))

[jtroo]

Hm I tried the altcode trick on Windows 11 with the default binary (not interception) and Windows seems to ignore the inputs whether or not I have numlock on. It does not output any special characters. I wonder if whatever Windows mechanism is responsible for the alt code outputs ignores SendInput events - which is what Kanata sends with the default binary. It wouldn't be the first time hah.

[VictorLemosR]

My assumption is that I can't write accented letters with normal us layout (btw, I'm on windows, should've said that before).

I tested all codes on deflocalkeys-win up to 650. After around 250, all codes were accepted and the values just kept repeating themselves in a cycle of about 200 (or even the 250, not sure). A lot of them were blank values (which I imagine some of them were the accented letters)

So I gave up on remapping the accented letters and went with international english (which permits dead keys). Just for curiosity, i went with all codes up to 300 and the exact same behaviour happened, also didn't find any accented letters

I assume if I change to a layout which uses them often (like portuguese, french, german) these codes should be recognizable

[VictorLemosR]

Btw, for future information, on international US layout, I'm able to use alt gr commands: AG-a -> á.

[gerhard-h]

maybe you could change ' or " so that tapping them will output ' or " but holding them starts the dead key behavior to type accented characters.

[VictorLemosR]

That's actually a nice idea. I'll try this solution after

[VictorLemosR]

Sadly, after a little testing, holding apostrophe to put accents on some letters isn't ideal. I'll just press apostrophe + space and leave dead keys as they are