<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/foot.git/wayland.h, branch 1.3.0</title>
<subtitle>A fast, lightweight and minimalistic Wayland terminal emulator</subtitle>
<id>https://git.0x0f.dev/mirrors/foot.git/atom?h=1.3.0</id>
<link rel='self' href='https://git.0x0f.dev/mirrors/foot.git/atom?h=1.3.0'/>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/'/>
<updated>2020-04-27T18:46:40Z</updated>
<entry>
<title>wayland: handle outputs disappearing</title>
<updated>2020-04-27T18:46:40Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-04-27T18:46:40Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=9cfe7200006ba8f996f3a005993a78f1da0236e1'/>
<id>urn:sha1:9cfe7200006ba8f996f3a005993a78f1da0236e1</id>
<content type='text'>
That is, deal with monitors being unplugged.

At least on Sway 1.4, surfaces are not unmapped before the output is
removed. Thus, in addition to free:ing the monitor resources, we also
need to update all terminals that are mapped on this output - remove
the output from their "mapped on" list.
</content>
</entry>
<entry>
<title>render: use output's subpixel mode when rasterizing glyphs</title>
<updated>2020-04-20T16:38:55Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-04-20T16:37:59Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=6f83ef81e54b2695692c76a0a06c94c53cb7e315'/>
<id>urn:sha1:6f83ef81e54b2695692c76a0a06c94c53cb7e315</id>
<content type='text'>
</content>
</entry>
<entry>
<title>input: slow trackpad scrolling now eventually scroll a line</title>
<updated>2020-04-10T16:43:29Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-04-10T16:43:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=00dbe12e4196a781bb320070569274e2f1793a4d'/>
<id>urn:sha1:00dbe12e4196a781bb320070569274e2f1793a4d</id>
<content type='text'>
Before, we converted each axis event's scroll amount to an integer and
scrolled that many lines.

However, axis events are speed sensitive - very slow scrolling will
result in events with a scroll amount that is &lt; 1.0.

For us, this meant we never scrolled a single line. You could slow
scroll all day if you wanted, and still we would never scroll a single
line.

Fix this by aggregating the scroll amount from axis events until the
scroll amount is &gt; 1.0, and then scroll.
</content>
</entry>
<entry>
<title>search: replace hard-coded key bindings with "user configurable" ones</title>
<updated>2020-03-18T14:30:14Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-03-18T14:30:14Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=04191564946d3ba6c1c49e5041e4bd0cda819043'/>
<id>urn:sha1:04191564946d3ba6c1c49e5041e4bd0cda819043</id>
<content type='text'>
They aren't really user configurable. At least not yet.

However, with this, we now handle raw key codes just like the normal
key bindings. Meaning, e.g. ctrl+g, ctrl+a, ctrl+e etc now works while
searching with e.g. a russian layout.
</content>
</entry>
<entry>
<title>input: bind key bindings to raw key codes too</title>
<updated>2020-03-18T13:29:34Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-03-18T13:29:34Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=6d30e7d15de49ba531cd8f8cd99c356d7f1ca0fc'/>
<id>urn:sha1:6d30e7d15de49ba531cd8f8cd99c356d7f1ca0fc</id>
<content type='text'>
Before, when looking for a matching user key binding, we only
matched *symbols*.

This means that the physical keys that generate a specific key binding
is layout dependent. What's worse, it may not even be possible to
generate the key binding at all.

Russian is one such layout, where all the "normal" (us) symbols are
replaced.

By using raw key codes, we can get around this - the key code has a
direct mapping to the physical key.

However, matching raw key codes **only** doesn't always make sense
either. For now, match **both** symbols _and_ key codes. Symbols take
precedence.

TODO: we might have to make this configurable _per binding_.

Note: 'search' mode still uses mostly hardcoded shortcuts that still
have this problem (i.e. ctrl+g doesn't work with a russian layout).
</content>
</entry>
<entry>
<title>wayland: store display FD in wayland struct</title>
<updated>2020-03-15T12:36:35Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-03-15T12:36:35Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=71fde3bfac37f4a67f33ecd7888ee6c134162a95'/>
<id>urn:sha1:71fde3bfac37f4a67f33ecd7888ee6c134162a95</id>
<content type='text'>
This way we:

* Don't have to call wl_display_get_fd() all the time
* No longer call fdm_del_no_close() even though the FD hasn't been
  added to the FDM.
</content>
</entry>
<entry>
<title>Merge branch 'scale-fonts-using-logical-dpi-plus-scale-factor'</title>
<updated>2020-03-13T17:48:15Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-03-13T17:48:15Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=59a1204c5080099b1d1d42a80d8aff94936ff3fa'/>
<id>urn:sha1:59a1204c5080099b1d1d42a80d8aff94936ff3fa</id>
<content type='text'>
</content>
</entry>
<entry>
<title>config: mouse-bindings: verify button isn't already mapped</title>
<updated>2020-03-12T09:46:27Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-03-12T09:46:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=c58f9a9ef93fd3fd2be711906b8214a53665e45f'/>
<id>urn:sha1:c58f9a9ef93fd3fd2be711906b8214a53665e45f</id>
<content type='text'>
A button may only be mapped to a single action. Detect when the user
tried to map the same button to multiple actions and error out.

To clear a binding (for example, to free up a button from the default
bindings), one can set the action it is bound to to
`NONE` (e.g. `primary-paste=NONE`).
</content>
</entry>
<entry>
<title>config/input: implement mouse bindings</title>
<updated>2020-03-12T09:20:05Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-03-12T09:20:05Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=45384839f0e9627cd5b376b045e11c14277d40d0'/>
<id>urn:sha1:45384839f0e9627cd5b376b045e11c14277d40d0</id>
<content type='text'>
* New config section, "mouse-bindings", where bindings are defined on
  the form "action=BTN_&lt;name&gt;
* pointer_button() handler now scans the bindings list instead of
  hardcoding primary-paste to BTN_MIDDLE.
* The implementation handles single- double- and triple clicks in the
  bindings, but there is currently no way to define anything but a
  single-click binding in the configuration.
</content>
</entry>
<entry>
<title>bindings: add minimize/maximize/fullscreen actions</title>
<updated>2020-03-12T08:34:09Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-03-12T08:34:09Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=65ff582358c07c8bb69f56dc8192c86d21b620d3'/>
<id>urn:sha1:65ff582358c07c8bb69f56dc8192c86d21b620d3</id>
<content type='text'>
These actions are by default not bound to anything.
</content>
</entry>
<entry>
<title>term: use logical DPI+scale factor when scaling fonts</title>
<updated>2020-03-11T15:10:55Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-03-11T15:10:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=acecab1c8bcb414521867fce46d238ad48f4b621'/>
<id>urn:sha1:acecab1c8bcb414521867fce46d238ad48f4b621</id>
<content type='text'>
This fixes an issue where the fonts were rendered too small when the
output had fractional scaling.

For integral scaling, using the logical (scaled) DPI multiplied with
the scaling factor results in the same final DPI value as if we had
used the physical DPI.

But for fractional scaling, this works around the fact that the
compositor downscales the surface after we've rendered it.

Closes #5
</content>
</entry>
<entry>
<title>search: add support for user configurable key bindings</title>
<updated>2020-03-08T14:28:47Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-03-08T14:28:47Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=0d188895c3e88f591aa47f7a5c272ad959e5a40d'/>
<id>urn:sha1:0d188895c3e88f591aa47f7a5c272ad959e5a40d</id>
<content type='text'>
No default bindings defined yet, though.
</content>
</entry>
<entry>
<title>input: convert the rest of the normal key bindings to configurable bindings</title>
<updated>2020-03-08T14:17:57Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-03-08T14:17:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=fcf483277568a7839708428cd30f53b01465cc04'/>
<id>urn:sha1:fcf483277568a7839708428cd30f53b01465cc04</id>
<content type='text'>
New actions defined and implemented:

* scrollback up/down
* font size up/down/reset
* spawn terminal

Break out key combo parsing to a new function,
parse_key_binding_for_action(). This function parses a string
containing one or more space separated key combo definitions on the
form (mod1+mod2+...+key), where key is a XKB key name (e.g. KP_Add).

Convert all hardcoded key bindings to configuration based
bindings. These still cannot actually be configured by the user, but
at least lives in the conf struct.
</content>
</entry>
<entry>
<title>wip: initial framework for dealing with key/mouse bindings in different modes</title>
<updated>2020-03-08T11:08:46Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-03-08T11:08:46Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=b22bb3097634206956392929795fd2902f08faa7'/>
<id>urn:sha1:b22bb3097634206956392929795fd2902f08faa7</id>
<content type='text'>
This adds initial support for defining key and mouse bindings that are
applied in different terminal modes/states.

For example, there are two arrays dealing with key and mouse bindings
in the "normal" mode. Most bindings will go here.

There's also an array for "search" mode. These bindings will be used
when the user has started a scrollback search.

In the future, there may be a model selection mode as well. Or maybe
"search" and "modal selection" will be combined into a single
"keyboard" mode. We'll see.

Since the keyboard bindings depend on the current XKB keymap,
translation from the user specified key combination string cannot be
done when loading the configuration, but must be done when we've
received a keymap from the wayland server.

We should explore if it's possible to load some kind of default keymap
just to be able to verify the validity of the key combination strings
at configuration load time, to be able to reject the configuration at
startup.

A couple of key bindings have been added as proof of concept.

Mouse bindings aren't handled at all yet, and is likely to be
re-written. For example, we can probably translate the configuration
strings at configuration load time.
</content>
</entry>
<entry>
<title>csd: initial implementation of minimize/maximize/close buttons</title>
<updated>2020-03-02T19:29:28Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-03-02T19:29:28Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=9699c9b8bfcbd7f9ebef5ee4ffe370cb03b1c8a2'/>
<id>urn:sha1:9699c9b8bfcbd7f9ebef5ee4ffe370cb03b1c8a2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>config: make CSD user configurable</title>
<updated>2020-03-02T17:42:49Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-03-02T17:42:49Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=22ce09eb44db887d32a5b3a88740939b7285c763'/>
<id>urn:sha1:22ce09eb44db887d32a5b3a88740939b7285c763</id>
<content type='text'>
The user can now configure the following:

* Whether to prefer CSDs or SSDs. But note that this is only a hint to
  the compositor - it may deny our request. Furthermore, not all
  compositors implement the decoration manager protocol, meaning CSDs
  will be used regardless of the user configuration (GNOME/mutter
  being the most prominent one).
* Title bar size and color, including transparency
* Border size and color, including transparency

Also drop support for rendering the CSDs inside the main surface.
</content>
</entry>
<entry>
<title>render: csd: split up positioning from rendering</title>
<updated>2020-02-29T17:02:38Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-02-29T17:02:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=92d638eb1c34859a08605ffc79be8f0a4a3c63a3'/>
<id>urn:sha1:92d638eb1c34859a08605ffc79be8f0a4a3c63a3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>input: cleanup</title>
<updated>2020-02-29T14:29:00Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-02-29T14:29:00Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=73133c10eed3ad8415646d42a3f6386d7d702348'/>
<id>urn:sha1:73133c10eed3ad8415646d42a3f6386d7d702348</id>
<content type='text'>
</content>
</entry>
<entry>
<title>input: csd: add a small delay before initiating a move</title>
<updated>2020-02-29T11:56:04Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-02-29T11:52:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=43b07b122a1fa460bdda3edc529726e3b6a6463d'/>
<id>urn:sha1:43b07b122a1fa460bdda3edc529726e3b6a6463d</id>
<content type='text'>
This ensures the user has time to double-click to toggle the maximized
state.
</content>
</entry>
<entry>
<title>wayland: remove all usages of wayl_terminal_from_surface()</title>
<updated>2020-02-29T11:13:58Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-02-29T11:13:58Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=c917a74f487941fa16548261680484cb78e63189'/>
<id>urn:sha1:c917a74f487941fa16548261680484cb78e63189</id>
<content type='text'>
Use the 'user data' pointer from the wayland surface instead.
</content>
</entry>
</feed>
