<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/foot.git/terminal.c, branch 1.0.0</title>
<subtitle>A fast, lightweight and minimalistic Wayland terminal emulator</subtitle>
<id>https://git.0x0f.dev/mirrors/foot.git/atom?h=1.0.0</id>
<link rel='self' href='https://git.0x0f.dev/mirrors/foot.git/atom?h=1.0.0'/>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/'/>
<updated>2019-12-05T18:34:47Z</updated>
<entry>
<title>term: determine cell width from the width of the space character</title>
<updated>2019-12-05T18:34:47Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2019-12-05T18:34:47Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=8dc956043158acb9fbabceb7a7f8d74f5c91a318'/>
<id>urn:sha1:8dc956043158acb9fbabceb7a7f8d74f5c91a318</id>
<content type='text'>
</content>
</entry>
<entry>
<title>term: test: set font DPI to the highest DPI we find</title>
<updated>2019-12-04T21:02:02Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2019-12-04T21:02:02Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=ad56afe2f4823043bf2adcf7815d1addb52ef48f'/>
<id>urn:sha1:ad56afe2f4823043bf2adcf7815d1addb52ef48f</id>
<content type='text'>
In most cases (i.e. when there's only a single output/monitor), this
will be *the* DPI value.

In other cases, well...

The _right_ thing to do is track the outputs our window is actually
mapped on, and re-instantiate fonts depending on the current output's
DPI. But that's for the future...
</content>
</entry>
<entry>
<title>fcft: font_from_name() no longer accepts a tllist</title>
<updated>2019-12-01T18:22:25Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2019-12-01T18:22:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=e9fbb371df911947b8effde7a926d23bad6530d8'/>
<id>urn:sha1:e9fbb371df911947b8effde7a926d23bad6530d8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>term: mouse reporting functions no longer take modifier state</title>
<updated>2019-11-30T16:11:00Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2019-11-30T16:11:00Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=fbeb1e96103681b6a3fac49443e64ed13ae28737'/>
<id>urn:sha1:fbeb1e96103681b6a3fac49443e64ed13ae28737</id>
<content type='text'>
The mouse reporting functions are called from input when we receive
Wayland mouse events.

We used to pass the current keyboard modifier (shift, alt, ctrl, etc)
to the terminal functions.

This however is wrong, since we may receive Wayland mouse events
without having keyboard focus. When we don't have keyboard focus, the
modifier state doesn't apply to us.

Remove the modifier arguments from the terminal mouse reporting
functions. These functions now read this state directly instead, but
only when the terminal instance in question has keyboard focus.
</content>
</entry>
<entry>
<title>term: add term_mouse_grabbed()</title>
<updated>2019-11-30T16:06:15Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2019-11-30T16:06:15Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=2208f4304b799dbaaf52629d8ef3ce5629f16184'/>
<id>urn:sha1:2208f4304b799dbaaf52629d8ef3ce5629f16184</id>
<content type='text'>
When this returns true, it means we have keyboard focus and are
grabbing the mouse (for e.g. selections), regardless of whether the
client has enabled mouse tracking or not.
</content>
</entry>
<entry>
<title>term: "raw" mouse mode requires shift only to be pressed</title>
<updated>2019-11-30T15:48:32Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2019-11-30T15:48:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=62ed0ef4f2705fb0300fdee419ba6114a71167b2'/>
<id>urn:sha1:62ed0ef4f2705fb0300fdee419ba6114a71167b2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>term: define xcursor strings as global variables</title>
<updated>2019-11-30T11:43:06Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2019-11-30T11:43:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=8f8ef5df0e7de8b8e8c8db3688a2ab8428fdce2a'/>
<id>urn:sha1:8f8ef5df0e7de8b8e8c8db3688a2ab8428fdce2a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>term: xcursor: use selection_enabled()</title>
<updated>2019-11-30T11:01:40Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2019-11-30T11:01:40Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=c8d94931e63010bdfb86cfa68b5f6f7c2b68d3e7'/>
<id>urn:sha1:c8d94931e63010bdfb86cfa68b5f6f7c2b68d3e7</id>
<content type='text'>
Instead of duplicating the code from selection_enabled() that deals
with forced selection, just call selection_enabled().

This was previously not possible since selection_enabled() didn't
require keyboard_focus. Now it does.
</content>
</entry>
<entry>
<title>term: reset: set 'origin' to ORIGIN_ABSOLUTE</title>
<updated>2019-11-29T23:32:06Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2019-11-29T23:32:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=a81c65caa2e5f4bbb5521f0382092f8eaa286310'/>
<id>urn:sha1:a81c65caa2e5f4bbb5521f0382092f8eaa286310</id>
<content type='text'>
</content>
</entry>
<entry>
<title>term: reset: don't access rows directly</title>
<updated>2019-11-29T22:36:04Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2019-11-29T22:36:04Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=8b7158703de69d0a3977491fd9a7ec17c86c4199'/>
<id>urn:sha1:8b7158703de69d0a3977491fd9a7ec17c86c4199</id>
<content type='text'>
We've just re-set the grid offsets, meaning rows 0..term-&gt;rows may not
all have been initialized.

Call grid_row_and_alloc() to ensure they are.
</content>
</entry>
<entry>
<title>term: xcursor: use 'hand2' instead of 'left_ptr' when mouse tracking</title>
<updated>2019-11-29T21:30:56Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2019-11-29T21:30:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=bf9a9e7b907d451b651ad78bf193cb8d66753f5a'/>
<id>urn:sha1:bf9a9e7b907d451b651ad78bf193cb8d66753f5a</id>
<content type='text'>
Mouse tracking always reports clicks, so using a cursor that suggests
you can click makes sense I think.
</content>
</entry>
<entry>
<title>term: xcursor cleanup</title>
<updated>2019-11-29T21:15:03Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2019-11-29T21:15:03Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=f41788c185d9fb5335fe1f3f191900db5e0792eb'/>
<id>urn:sha1:f41788c185d9fb5335fe1f3f191900db5e0792eb</id>
<content type='text'>
Show 'text' cursor when:

* we have no mouse tracking enabled
* forced selection has been enabled (shift being held down)
* We're *not* scrollback searching

In all other cases, show the 'left_ptr' cursor.
</content>
</entry>
<entry>
<title>terminal: use the 'text' xcursor pointer whenever selection is possible</title>
<updated>2019-11-28T18:35:47Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2019-11-28T18:35:47Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=0dd37f0a364fc36284dad17e8fb1345714261a4a'/>
<id>urn:sha1:0dd37f0a364fc36284dad17e8fb1345714261a4a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>async: first synchronous write may succeed partially</title>
<updated>2019-11-28T18:20:25Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2019-11-28T18:20:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=903581b7eb05a566373eb784eeb958b9cd792493'/>
<id>urn:sha1:903581b7eb05a566373eb784eeb958b9cd792493</id>
<content type='text'>
When trying to write (to e.g. the slave, or to a clipboard receiver),
we first try to send the data synchronously, and only if that fails do
we switch to asynchronous mode.

However, the first synchronous may (in fact, is likely to) succeed
partially.
</content>
</entry>
<entry>
<title>font: pass dpi=96 to fontconfig</title>
<updated>2019-11-26T18:02:35Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2019-11-26T17:55:23Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=ae91c53fb2aea05f13d98edc1f80bbb56e1f28f3'/>
<id>urn:sha1:ae91c53fb2aea05f13d98edc1f80bbb56e1f28f3</id>
<content type='text'>
TODO: use actual output PPI. Question is *which* output...
</content>
</entry>
<entry>
<title>font: move metrics from terminal struct to font struct</title>
<updated>2019-11-26T18:02:35Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2019-11-26T17:54:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=bc86cd61c75f984633eb226692a30832c58efb17'/>
<id>urn:sha1:bc86cd61c75f984633eb226692a30832c58efb17</id>
<content type='text'>
</content>
</entry>
<entry>
<title>term: shutdown: handle *not* being unmapped</title>
<updated>2019-11-21T17:18:35Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2019-11-21T17:18:35Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=ee45c48debd186c70860351b5d44bb57d5823706'/>
<id>urn:sha1:ee45c48debd186c70860351b5d44bb57d5823706</id>
<content type='text'>
When we're shutting down a terminal, we destroy our Wayland window,
and assume that will unmap us.

There are cases when this isn't true (most likely when e.g. a screen
locker is active, and the unmap is being deferred).

Handle by explicitly setting focused to NULL.
</content>
</entry>
<entry>
<title>fonts: use 'weight' and 'slant', not 'style' when loading fonts</title>
<updated>2019-11-19T16:35:02Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2019-11-19T16:35:02Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=3c8a87168aa74e19665a2b43e2e242fbc72898b8'/>
<id>urn:sha1:3c8a87168aa74e19665a2b43e2e242fbc72898b8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>term: report_mouse_click(): legacy mode only supports rows/cols up to 223.</title>
<updated>2019-11-18T10:31:21Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2019-11-18T10:31:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=7ff5a8027a9f5b520132f5c85d3d22cb9c1db084'/>
<id>urn:sha1:7ff5a8027a9f5b520132f5c85d3d22cb9c1db084</id>
<content type='text'>
In the legacy mouse reporting mode, line and column numbers are
limited to 223 (255-32). In case the current coordinate falls outside
this, simply ignore it (don't report it).
</content>
</entry>
<entry>
<title>term: assert(false) on MOUSE_X10</title>
<updated>2019-11-18T10:18:48Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2019-11-18T10:18:48Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=832cc8c2697115e19015296e6580e40641e12357'/>
<id>urn:sha1:832cc8c2697115e19015296e6580e40641e12357</id>
<content type='text'>
This mouse mode is never enabled. I.e. we don't support it. Add
asserts to catch usage of it, should we ever decide to implement it.
</content>
</entry>
</feed>
