14:36 <anarcat> dnkl: ah! i *knew* i had seen this somewhere... didn't find it in the FAQ!

14:37 <anarcat> thanks!

20:29 <Consolatis> I am currently playing around with xdg_activation, I am aware that foot a) requests and forwards a token before calling xdg-open b) uses the protocol without setting a serial to try to activate itself. However b) might not work if the compositor does focus-stealing-prevention, e.g. only creates valid tokens when the requester had the focus while requesting the token.

20:30 <Consolatis> But as foot is also capable of sending desktop notifications by calling an external command and the same could be done by user configuration when seeing a BELL character, I wonder if that could be enhanced to asynchronously read the output of the spawed application and then use that output (or part of it) as an xdg_activation token to activate itself.

20:31 <Consolatis> that would allow foot to execute a command which spawns a notification, wait for a xdg_activation token when the user clicks on the notification and then try to active itself

20:33 <Consolatis> and all that without having to depend on dbus

21:04 <Consolatis> really bad example how to get the activation token on click of the notification: G_MESSAGES_DEBUG=all notify-send --action=default="Activate Foot" header body

21:05 <Consolatis> but there is nothing stopping anybody to write a small tool that has a sane output, it would just be a question for foot to define a format that i can easily parse

21:05 <Consolatis> it*

21:11 <Consolatis> e.g. more like G_MESSAGES_DEBUG=all notify-send --action=default="foobar barfoo" header body | sed -n '/Activation Token/ s/^.*Activation Token: \(.*\)$/\1/ p'