Desktop notifications protocol: Add support for specifying urgency

This commit is contained in:
Kovid Goyal
2024-05-16 21:38:43 +05:30
parent 176dab37d9
commit 865f662216
3 changed files with 19 additions and 4 deletions

View File

@@ -70,6 +70,8 @@ Detailed list of changes
- Wayland: Fix infinite loop causing bad performance when using IME via fcitx5 due to a change in fcitx5 (:iss:`7396`)
- Desktop notifications protocol: Add support for specifying urgency
- Improve rendering of Unicode shade character to avoid Moire patterns (:pull:`7401`)
- kitten @ send-key: Fix some keys being sent in kitty keyboard protocol encoding when not using socket for remote control

View File

@@ -120,12 +120,16 @@ Key Value Default Description
and not visible to the user, for example, because it is in an inactive tab or
its OS window is not currently active.
``always`` is the default and always honors the request.
``u`` ``0, 1 or 2`` ``unset`` The *urgency* of the notification. ``0`` is low, ``1`` is normal and ``2`` is critical.
If not specified normal is used.
======= ==================== ========== =================
.. note::
.. versionadded:: 0.35.0
Support for the ``u`` key to specify urgency
.. versionadded:: 0.31.0
Support for the ``o`` key to prevent notifications from focused windows
was added in kitty version 0.31.0
.. note::