I've noticed that the way gurk handles attachment paths trows off xdg-open. I can't quite trace how/when this happens but gurk calls xdg-open with a url for some images/videos:
file:///home/stanislav/.local/share/gurk/files/2026-02-20/screenshot-2026-02-20T09:53:01-0400.png
and an absolute path for others:
/home/stanislav/.local/share/gurk/files/2026-02-18/59126bc1.png
The url format throws off some image viewers such as nsxiv.
Since gurk already seems fine sending absolute paths sometimes (perhaps after caching?), it might make things easier for people to more consistently adopt the path format.
I've setup up a wrapper script to help xdg deal with common attachments in the meantime.
I've noticed that the way gurk handles attachment paths trows off
xdg-open. I can't quite trace how/when this happens but gurk calls xdg-open with a url for some images/videos:file:///home/stanislav/.local/share/gurk/files/2026-02-20/screenshot-2026-02-20T09:53:01-0400.png
and an absolute path for others:
/home/stanislav/.local/share/gurk/files/2026-02-18/59126bc1.png
The url format throws off some image viewers such as nsxiv.
Since gurk already seems fine sending absolute paths sometimes (perhaps after caching?), it might make things easier for people to more consistently adopt the path format.
I've setup up a wrapper script to help xdg deal with common attachments in the meantime.