Repository navigation
Releases
Releases · tiagosantini/opencode-kde-notify
v0.2.0
Added
- Clicking a notification brings the terminal running OpenCode back: it leaves "show desktop",
unminimizes the window, switches to its Plasma Activity and virtual desktop, raises and focuses
it, also on another monitor (KWin scripting over D-Bus; Wayland and X11). - The matching OpenCode session tab is focused on click; under tmux the pane's window is selected
too. focusOnClickoption andOPENCODE_KDE_NOTIFY_FOCUS_ON_CLICKenvironment variable (default
true).focusCommandoption andOPENCODE_KDE_NOTIFY_FOCUS_COMMANDenvironment variable for exact
window selection or desktops without KWin scripting.CHANGELOG.md.
Changed
- Notifications carry a hidden
defaultaction; a short-livednotify-send --waitchild receives
the click and exits with the bubble. - Click support degrades gracefully: notifications stay non-interactive when libnotify is older
than 0.8, when the server lacks action support, or when the session is not KDE. - Rapid clicks are coalesced into one focus run, and click waiters are stopped when OpenCode exits,
so no orphaned processes or temporary focus scripts are left behind.
v0.1.1
Notification history
Plasma only keeps a notification in the system tray history when it can attribute it to an
application. It resolves the desktop-entry hint against an installed .desktop file; without one
the notification lands in the @other bucket, which plasma-workspace ships with
ShowInHistory=false — the bubble appeared, the history stayed empty.
This release:
- sends
--hint=string:desktop-entry:opencode; - installs
~/.local/share/applications/opencode.desktopon startup (NoDisplay, marked with
X-OpenCode-KDE-Notify=true, so a realopencode.desktopfrom another source is never touched); - adds the
desktopEntryoption andOPENCODE_KDE_NOTIFY_DESKTOP_ENTRYenvironment variable to
turn the file off.
Note that Plasma keeps the history in memory, so it is emptied whenever plasmashell restarts
(KDE bug 486483).