<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/foot.git/CHANGELOG.md, branch 1.18.1</title>
<subtitle>A fast, lightweight and minimalistic Wayland terminal emulator</subtitle>
<id>https://git.0x0f.dev/mirrors/foot.git/atom?h=1.18.1</id>
<link rel='self' href='https://git.0x0f.dev/mirrors/foot.git/atom?h=1.18.1'/>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/'/>
<updated>2024-08-14T10:00:08Z</updated>
<entry>
<title>changelog: prepare for 1.18.1</title>
<updated>2024-08-14T10:00:08Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2024-08-14T10:00:08Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=447b02b530e62ff901539131e9c15d4ef6c592cc'/>
<id>urn:sha1:447b02b530e62ff901539131e9c15d4ef6c592cc</id>
<content type='text'>
</content>
</entry>
<entry>
<title>osc: regression: fix OSC-111 handling of alpha changes</title>
<updated>2024-08-14T06:53:45Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2024-08-14T06:50:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=2896c1898127256193d49c80a56ba7188fad0e33'/>
<id>urn:sha1:2896c1898127256193d49c80a56ba7188fad0e33</id>
<content type='text'>
When the background alpha changes from fully opaque, to transparent,
or vice versa, we need to do more than just repaint the affected
cells.

For example, we need to create new surfaces with the correct pixel
format.

OSC-11 (set background color) already does this, but the same alpha
checking logic was missing in OSC-111 (reset background color).

Fixes #1801
</content>
</entry>
<entry>
<title>input: CSD buttons are now triggered when releasing the mouse button</title>
<updated>2024-08-09T06:20:36Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2024-08-02T15:12:12Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=7ec9ca2b9528126bf11dda37cfea9687b6bc66a3'/>
<id>urn:sha1:7ec9ca2b9528126bf11dda37cfea9687b6bc66a3</id>
<content type='text'>
This is how most UIs work.

Note that we (at least on River) don't get any surface enter/leave
events while a button is held. This means we can't detect if the user
pressed the mouse button while on a CSD button, but then moves the
mouse outside. Releasing the mouse button will still activate the CSD
button.

Closes #1787
</content>
</entry>
<entry>
<title>changelog: osc-99: sound support</title>
<updated>2024-08-04T13:23:33Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2024-08-04T13:23:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=fb74a2df2766f9f43f6ed6b5020aab25925c671b'/>
<id>urn:sha1:fb74a2df2766f9f43f6ed6b5020aab25925c671b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>changelog: add new 'unreleased' section</title>
<updated>2024-08-02T12:33:26Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2024-08-02T12:33:26Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=62b0b65d4712abd9ecd21ec2fe684c87a868bcc1'/>
<id>urn:sha1:62b0b65d4712abd9ecd21ec2fe684c87a868bcc1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>changelog: prepare for 1.18.0</title>
<updated>2024-08-02T12:27:57Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2024-08-02T12:27:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=1272632f3b0b6e5e21675374426732d0b5b4a25b'/>
<id>urn:sha1:1272632f3b0b6e5e21675374426732d0b5b4a25b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>changelog: more template parameters we've added to desktop-notifications</title>
<updated>2024-08-02T08:18:59Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2024-08-02T08:18:59Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=901daefd960cb666c0da8ca20e574ed40f1f4cf2'/>
<id>urn:sha1:901daefd960cb666c0da8ca20e574ed40f1f4cf2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>osc: kitty notifications: cleanup and update to latest version of spec</title>
<updated>2024-08-02T06:07:13Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2024-08-02T06:07:13Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=ea2f0e7c3f29f2ba83ad71e36c6751bb571f826f'/>
<id>urn:sha1:ea2f0e7c3f29f2ba83ad71e36c6751bb571f826f</id>
<content type='text'>
* Don't store a list of unfinished notifications. Use a single one. If
  the notification ID of the 'current' notification doesn't match the
  previous, unfinished one, the 'current' notification replaces the
  previous one, instead of updating it.

* Update xstrjoin() to take an optional delimiter (for example ','),
  and use that when joining categories and 'alive IDs'.

* Rename ${action-arg} to ${action-argument}

* Update handling of the 'n' parameter (symbolic icon name); the spec
  allows it to be used multiple times, and the terminal is supposed to
  pick the first one it can resolve. Foot can't resolve icons at all,
  neither can 'notify-send' or 'fyi' (which is what foot typically
  executes to display a notification); it's the notification daemon that
  resolves icons.

  The spec _could_ be interpreted to mean the terminal should lookup
  .desktop files, and use the value of the 'Icon' key from the first
  matching .desktop files. But foot doesn't read .desktop files, and I
  don't intend to implement XDG directory scanning and parsing of
  .desktop files just to figure out which icon to use.

  Instead, use a simple heuristics; use the *shortest* symbolic
  names. The idea is pretty simple: plain icon names are typically
  shorter than .desktop file IDs.
</content>
</entry>
<entry>
<title>osc: kitty notifications: implement the 'close' request</title>
<updated>2024-07-25T17:24:28Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2024-07-25T17:24:28Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=c4d9f8a8ff4d65b43defb8d63e775e8b91f82bed'/>
<id>urn:sha1:c4d9f8a8ff4d65b43defb8d63e775e8b91f82bed</id>
<content type='text'>
Add a new config option, desktop-notifications.close, defining what to
execute to close a notification. It has a single template parameter,
${id}, that is expanded to the external notification ID foot may have
picked up from the notification helper.

notify-send does not support closing notifications, and it appears
impossible to pass an *unsigned* integer as argument to gdbus. Hence
no default value for the new 'close' option.

Example:

    printf '\e]99;i=123;this is a notification\e\\'
    printf '\e]99;i=123:p=close;\e\\'
</content>
</entry>
<entry>
<title>notify: split up the ${action} template parameter</title>
<updated>2024-07-23T17:08:21Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2024-07-23T17:08:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=ecbec57a4749cc4162d2bb55dd14e1890b6dff31'/>
<id>urn:sha1:ecbec57a4749cc4162d2bb55dd14e1890b6dff31</id>
<content type='text'>
Split it up into two, ${action-name} and ${action-label}.

Dunstify, for example, has a different syntax compared to notify-send:

notify-send: default=foobar
dunstify: default,foobar
</content>
</entry>
<entry>
<title>notify: don't focus/report on notification dismissal</title>
<updated>2024-07-23T14:41:52Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2024-07-23T14:41:52Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=045ead985c1e320f289704b6a995d48a5eccf59e'/>
<id>urn:sha1:045ead985c1e320f289704b6a995d48a5eccf59e</id>
<content type='text'>
Only do it when the notification was activated.

Here, activated means the 'click to activate' notification action was
triggered.

How do we tie everything together?

First, we add a new template parameter, ${action}. It's intended to be
used with e.g. notify-send's --action option.

When the action is triggered, notify-send prints its name on stdout,
on a separate line. Look for this in stdout. Only if we've seen it do
we focus/report the notification.
</content>
</entry>
<entry>
<title>changelog: new desktop-notifications config section</title>
<updated>2024-07-23T05:17:21Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2024-07-23T05:09:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=0209458cc0b4fc502492253d3a9e9338e590a97e'/>
<id>urn:sha1:0209458cc0b4fc502492253d3a9e9338e590a97e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>osc/notify: add support for OSC-99, kitty desktop notifications</title>
<updated>2024-07-23T05:17:21Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2024-07-19T13:04:28Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=b0bf8ca5f7034f6d95bc3b58082e719a81d99859'/>
<id>urn:sha1:b0bf8ca5f7034f6d95bc3b58082e719a81d99859</id>
<content type='text'>
This adds limited support for OSC-99, kitty desktop notifications[^1]. We
support everything defined by the "protocol", except:

* 'a': action to perform on notification activation. Since we don't
  trigger the notification ourselves (over D-Bus), we don't know a)
  which ID the notification got, or b) when it is clicked.
* ... and that's it. Everything else is supported

To be explicit, we *do* support:

* Chunked notifications (d=0|1), allowing the application to append
  data to a notification in chunks, before it's finally displayed.
* Plain UTF-8, or base64-encoded UTF-8 payload (e=0|1).
* Notification identifier (i=xyz).
* Payload type (p=title|body).
* When to honor the notification (o=always|unfocused|invisible), with
  the following quirks:
    - we don't know when the window is invisible, thus it's treated as
      'unfocused'.
    - the foot option 'notify-focus-inhibit' overrides 'always'
* Urgency (u=0|1|2)

[^1]: https://sw.kovidgoyal.net/kitty/desktop-notifications/
</content>
</entry>
<entry>
<title>input: allow mouse selections to start inside the margins</title>
<updated>2024-07-19T04:55:28Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2024-07-18T06:08:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=45c7cd3f7472b11d50622b10867a329b4d8e2451'/>
<id>urn:sha1:45c7cd3f7472b11d50622b10867a329b4d8e2451</id>
<content type='text'>
Before this, margins were special cased:

* The mouse cursor was always a pointer, and never an I-beam (thus
  signaling selections cannot be made).
* The internal mouse coords where set to -1 when the cursor was inside
  the margins, causing:
    - text selections from being made
    - mouse events being passed to mouse grabbing applications

In particular, even with a one-pixel margin, making selections was
unnecessarily hard in e.g. fullscreen mode, where you'd expect to be
able to throw the cursor into the corner of the screen and then start
a selection.

With this patch, the cursor is treated as if it was in the first/last
column/row, when inside the margin(s).

An unintended side-effect of this, initially, was that auto-scrolling
selections where way too easy to trigger, since part of its logic is
checking if the cursor is inside the margins.

That problem has been reduced by two things:

* auto-scrolling does not occur unless a selection has been
  started. That is, just holding down the mouse in the margins and
  moving up/down doesn't cause scrolling. You have to first select at
  least one cell in the visible viewport.
* A selection isn't fully started (i.e. a cell is actually selected)
  unless the cursor is inside the actual grid, and *not* in the
  margins.

What does the last point mean? We now allow a selection to be
_started_ when clicking in the margin. What this means internally is
we set a start coordinate for a selection, but *not* and end
coordinate. At this point, we don't have an actual selection. Nothing
is selected, and no cells are highlighted, graphically.

This happens when we set an end coordinate. Without the last bullet
point, that would happen as soon as the cursor was _moved_, even if
still inside the margins. Now, we require the cursor to leave the
margins and touch an actual cell before we set an end coordinate.

Closes #1702
</content>
</entry>
<entry>
<title>csi: in-band window resize notifications, private mode 2048</title>
<updated>2024-07-19T04:54:32Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2024-06-30T17:44:17Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=38461eef6f3b612277bf48e49b9cc6c3b79e25bb'/>
<id>urn:sha1:38461eef6f3b612277bf48e49b9cc6c3b79e25bb</id>
<content type='text'>
This implements
https://gist.github.com/rockorager/e695fb2924d36b2bcf1fff4a3704bd83,
in-band window resize notifications.

When user enables private mode 2048 (in-band resize
notifications), *always* send current size, even if the mode is
already active.

This ensures applications can rely on getting a reply from the
terminal.
</content>
</entry>
<entry>
<title>log: respect the NO_COLOR environment variable</title>
<updated>2024-07-18T06:44:30Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2024-07-18T06:41:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=36e4435bbfbb1a10724e0161f0ca1c0b8bf1bc7c'/>
<id>urn:sha1:36e4435bbfbb1a10724e0161f0ca1c0b8bf1bc7c</id>
<content type='text'>
http://no-color.org/

Closes #1771
</content>
</entry>
<entry>
<title>themes: catppuccin: replace with updated flavors</title>
<updated>2024-07-18T06:21:14Z</updated>
<author>
<name>abs3nt</name>
<email>abs3nt@asdf.cafe</email>
</author>
<published>2024-07-14T20:26:31Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=1fd40760828ee2e2f159c3a8f7b19c3c348814dd'/>
<id>urn:sha1:1fd40760828ee2e2f159c3a8f7b19c3c348814dd</id>
<content type='text'>
Pulled from https://github.com/catppuccin/foot
</content>
</entry>
<entry>
<title>input: don't map wheel events to BTN_{BACK,FORWARD}</title>
<updated>2024-07-13T08:41:10Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2024-07-13T08:24:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=1136108c9780eae9fae252a1bca5089f19fcd57d'/>
<id>urn:sha1:1136108c9780eae9fae252a1bca5089f19fcd57d</id>
<content type='text'>
BTN_BACK and BTN_FORWARD are separate buttons. The scroll wheel don't
have any button mappings in libinput/wayland, so make up our own
defines.

This allows us to map them in mouse bindings.

Also expose BTN_WHEEL_{LEFT,RIGHT}. These were already defined, and
used, internally, to handle wheel tilt events. With this, they can
also be used in mouse bindings.

Finally, fix encoding used for BTN_{BACK,FORWARD} when sending mouse
button events to the client application. Before this, they were mapped
to buttons 4/5. But, button 4/5 are for the scroll wheel, and as
mentioned above, BTN_{BACK,FORWARD} are not the same as scroll wheel
"buttons".

Closes #1763
</content>
</entry>
<entry>
<title>changelog: remove entry for change that hasn't yet been merged</title>
<updated>2024-07-13T08:40:37Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2024-07-13T08:40:37Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=15c0078c2dfcb956fc98d68a7dfec99bea2eb726'/>
<id>urn:sha1:15c0078c2dfcb956fc98d68a7dfec99bea2eb726</id>
<content type='text'>
</content>
</entry>
<entry>
<title>render: hollow-cursor: use correct cursor color</title>
<updated>2024-07-13T08:37:21Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2024-07-13T08:22:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=56556e5f237025619820a3c8595e0de9d2b1c230'/>
<id>urn:sha1:56556e5f237025619820a3c8595e0de9d2b1c230</id>
<content type='text'>
</content>
</entry>
</feed>
