<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/foot.git/input.c, branch releases/1.10</title>
<subtitle>A fast, lightweight and minimalistic Wayland terminal emulator</subtitle>
<id>https://git.0x0f.dev/mirrors/foot.git/atom?h=releases%2F1.10</id>
<link rel='self' href='https://git.0x0f.dev/mirrors/foot.git/atom?h=releases%2F1.10'/>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/'/>
<updated>2021-12-08T17:06:10Z</updated>
<entry>
<title>kitty: simplify: always calculate alternate/base keys</title>
<updated>2021-12-08T17:06:10Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2021-12-07T21:22:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=352077c78aaf4e51759e37d1279d3c8ce7d70600'/>
<id>urn:sha1:352077c78aaf4e51759e37d1279d3c8ce7d70600</id>
<content type='text'>
But only _emit_ them if report alternate has been enabled.
</content>
</entry>
<entry>
<title>kitty: when emitting associated text, don’t report mods/events unless necessary</title>
<updated>2021-12-08T17:06:08Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2021-12-07T20:52:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=30a66996b2dc57406311bb140d0aa988bcd19488'/>
<id>urn:sha1:30a66996b2dc57406311bb140d0aa988bcd19488</id>
<content type='text'>
</content>
</entry>
<entry>
<title>kitty: report-alternate: apply base-layout key to composed characters</title>
<updated>2021-12-08T17:06:06Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2021-12-07T20:48:42Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=db95a90e57a8dfd60856599df7cb26a8d38fb4aa'/>
<id>urn:sha1:db95a90e57a8dfd60856599df7cb26a8d38fb4aa</id>
<content type='text'>
</content>
</entry>
<entry>
<title>kitty: implement “base layout key” in “report alternate key”</title>
<updated>2021-12-08T17:06:04Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2021-12-07T19:25:14Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=7e9ca65f4d84a9578e604af5632c19cd9cc16101'/>
<id>urn:sha1:7e9ca65f4d84a9578e604af5632c19cd9cc16101</id>
<content type='text'>
</content>
</entry>
<entry>
<title>kitty: initial support for “report alternate key”</title>
<updated>2021-12-08T17:06:02Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2021-12-07T18:55:52Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=010c4001d2f83aaf1f5c86455c8e5bd4ba708cc7'/>
<id>urn:sha1:010c4001d2f83aaf1f5c86455c8e5bd4ba708cc7</id>
<content type='text'>
In this mode, the “shifted” and “base layout” keys are added to the
CSIs, as sub-parameters to the “key” parameter.

Note that this PR only implements the “shifted” key, not the “base
layout key”.

This is done by converting the original XKB symbol to it’s
corresponding UTF-32 codepoint. If this codepoint is different from
the one we use as “key” in the CSI, we add it as a sub-parameter.

Related to #319
</content>
</entry>
<entry>
<title>kitty: only emit plain text on key press- and repeat events</title>
<updated>2021-12-08T17:05:56Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2021-12-07T19:26:12Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=f3f3f600404d4c565e8223df61220e483e382491'/>
<id>urn:sha1:f3f3f600404d4c565e8223df61220e483e382491</id>
<content type='text'>
That is, release events always generate CSIs
</content>
</entry>
<entry>
<title>kitty: add ISO_Level{3,5}_Shift keys</title>
<updated>2021-12-08T17:05:51Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2021-12-07T18:11:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=40b69ab52182f75663c6fe516f75f83f576915b1'/>
<id>urn:sha1:40b69ab52182f75663c6fe516f75f83f576915b1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>kitty: composed characters with “report associated text”</title>
<updated>2021-12-08T17:05:49Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2021-12-07T06:31:34Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=305f3122b164342b65c73a21d32c5188048e7dbe'/>
<id>urn:sha1:305f3122b164342b65c73a21d32c5188048e7dbe</id>
<content type='text'>
The generic input handler now converts the composed character to it’s
UTF-32 equivalent. This means we now provide a valid UTF-32 codepoint
for both composed characters, and non-composed (plain-text)
characters.

Use this in the kitty protocol to simplify the logic around composed
characters, by simply treating them as plain text.
</content>
</entry>
<entry>
<title>kitty: implement “report associated text”</title>
<updated>2021-12-08T17:05:46Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2021-12-06T22:01:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=7a5386d883c8b7cb4f23c13da948bd57c1eb3bf4'/>
<id>urn:sha1:7a5386d883c8b7cb4f23c13da948bd57c1eb3bf4</id>
<content type='text'>
In this mode, key events that generate text now add a third CSI
parameter, indicating the actual codepoint.

Remember that we always use the *unshifted* key in the CSI
escapes. With this mode, those CSI escapes now also included the text
codepoint. I.e. what would have been emitted, had we not generated a
CSI escape.

As far as I can tell, this mode has no effect unless “report all keys
as escape sequences” is enabled (reason being, without that, there
aren’t any text events that generate CSIs - they’re always emitted
as-is).

Note that Kitty itself seems to be somewhat buggy in this mode. At
least on Wayland, with my Swedish layout. For example ‘a’ and ‘A’ does
generate the expected CSIs, but ‘å’ and ‘Å’ appears to be treated as
non-text input.

Furthermore, Kitty optimizes away the modifier parameter, if no
modifiers are pressed (e.g. CSI 97;;97u), while we always emit the
modifier (CSI 97;1;97u).

Related to #319
</content>
</entry>
<entry>
<title>input: kitty: add support for “report all keys as escape codes”</title>
<updated>2021-12-08T17:05:33Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2021-11-29T20:03:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=4e34fb8fb7006a3d5d9d458e220fffef47c97de6'/>
<id>urn:sha1:4e34fb8fb7006a3d5d9d458e220fffef47c97de6</id>
<content type='text'>
</content>
</entry>
<entry>
<title>input: kitty: merge handling of plain-text and composed characters</title>
<updated>2021-12-08T17:03:52Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2021-11-29T19:13:23Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=85b10675146566f6912ef16690c6318faf3678b2'/>
<id>urn:sha1:85b10675146566f6912ef16690c6318faf3678b2</id>
<content type='text'>
All plain-text and composed characters are now printed as-is, in a
single place.

Also fix handling of “generic” keys when emitted as escapes; don’t use
the raw XKB symbol as key in the escape, convert it to a unicode code
point first. For many symbols, these are the same. But not
all.

For now, we fallback to using the symbol as is if XKB fails to convert
it to a codepoint. Not sure if we should simply drop the key press
instead.

Composed characters also need special treatment; we can’t use the
symbol as is, since it typically refers to the last key
pressed (i.e. not the composed character). And, that key is
also (usually) a special “dead” key, which cannot be converted to a
unicode codepoint.

So, what we do is convert the generated utf8 string, and (try to)
convert it to a wchar. If it succeeds, use that. If not, fallback to
using the XKB symbol (as above).
</content>
</entry>
<entry>
<title>input: reset compose state on key *releases*, not presses</title>
<updated>2021-12-08T17:03:51Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2021-11-29T19:12:49Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=149e978bc4281bd0d7ad1fd345ad2b843458d6d8'/>
<id>urn:sha1:149e978bc4281bd0d7ad1fd345ad2b843458d6d8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>input: kitty: treat repeating == pressed when report-events is off</title>
<updated>2021-12-08T17:03:48Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2021-11-28T18:20:37Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=5d94b02a03877adf85f4e4f721d4f1adaece5397'/>
<id>urn:sha1:5d94b02a03877adf85f4e4f721d4f1adaece5397</id>
<content type='text'>
</content>
</entry>
<entry>
<title>input: kitty: add support for the “report event” mode (0b10)</title>
<updated>2021-12-08T17:03:42Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2021-11-28T17:45:28Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=30f60259cc13fd13d483b8e6cd36338324735eb9'/>
<id>urn:sha1:30f60259cc13fd13d483b8e6cd36338324735eb9</id>
<content type='text'>
</content>
</entry>
<entry>
<title>input: don’t ignore key release events</title>
<updated>2021-12-08T17:03:39Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2021-11-28T15:36:14Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=71606009fda541132de0f12c2b68b9e69c5bc7f7'/>
<id>urn:sha1:71606009fda541132de0f12c2b68b9e69c5bc7f7</id>
<content type='text'>
Before this, key release events stopped the repeat timer, and then
returned.

Now, we run through the entire function. Most things are still only
done on key press events. But, the goal here is to get to the keyboard
protocol functions (and the kitty protocol in particular), and call
them on release events too.

This is in preparation for the kitty protocol mode 0b10, report event
types.
</content>
</entry>
<entry>
<title>input: always update the xcursor shape in pointer enter/motion events</title>
<updated>2021-12-01T19:04:01Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2021-12-01T19:04:01Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=1619e83c13875f71f79e5ca0e4504dd59dd81d79'/>
<id>urn:sha1:1619e83c13875f71f79e5ca0e4504dd59dd81d79</id>
<content type='text'>
Now that term_xcursor_update_for_seat() takes the current surface into
account (i.e. doesn’t assume the cursor is over the main grid),
there’s no longer any need to call render_xcursor_set() directly.

Thus, we can simply call term_xcursor_update_for_seat() on **all**
pointer enter and motion events. As long as we take care to update the
internal state to reflect the, possibly new, current surface before
doing so.

Also make sure to **always** reset the seat’s “current” xcursor
pointer on pointer leave events. This is done without actually sending
anything to the compositor, but is necessary to ensure that we *do*
send a request to update the xcursor on the next pointer enter event.
</content>
</entry>
<entry>
<title>input: fix debug log format specifier; ‘count’ is a size_t</title>
<updated>2021-12-01T19:03:18Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2021-12-01T19:03:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=63e8b1b2924aef94316e621513fd938eb0acc4e9'/>
<id>urn:sha1:63e8b1b2924aef94316e621513fd938eb0acc4e9</id>
<content type='text'>
</content>
</entry>
<entry>
<title>input: make csd_data variable ‘const’</title>
<updated>2021-11-30T21:15:13Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2021-11-30T21:15:13Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=fce13c4106afa3509536802d2c7d74e4d8b8e50d'/>
<id>urn:sha1:fce13c4106afa3509536802d2c7d74e4d8b8e50d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'window-menu'</title>
<updated>2021-11-30T21:10:27Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2021-11-30T21:10:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=90cfdcf1a5ddbaad44a46fb88b8dbafd319ee0ad'/>
<id>urn:sha1:90cfdcf1a5ddbaad44a46fb88b8dbafd319ee0ad</id>
<content type='text'>
</content>
</entry>
<entry>
<title>input: regression: reset view (and cancel selection) on “handled” input</title>
<updated>2021-11-29T18:31:48Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2021-11-29T18:31:48Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=73a048f9d37af86264c5c48b7889e20f3e57f693'/>
<id>urn:sha1:73a048f9d37af86264c5c48b7889e20f3e57f693</id>
<content type='text'>
This fixes a regression, where the view (and selection) was only reset
if the keyboard input resulted in plain text. That is, key presses
like enter, arrows etc did not.
</content>
</entry>
</feed>
