14:18 <rjarry> hey all, I've asked over on #weechat but my problem seems to be related to foot

14:19 <rjarry> basically, when running weechat in alacritty (or other term emulators), a bell character activates the urgent flag

14:19 <rjarry> this is not working in foot

14:20 <rjarry> when I exit weechat, echo -e '\a' >&2 does set the urgent flag though

14:20 <rjarry> there seems to be a weird interaction between weechat and foot which I don't understand

14:21 <rjarry> if anybody already experienced this and has a fix, it would be much appreciated

14:21 <dnkl> rjarry: this is documented in the foot.ini man page

14:21 <dnkl> https://codeberg.org/dnkl/foot/src/branch/master/doc/foot.ini.5.scd#L363

14:22 <rjarry> dnkl: yes, I have that enabled

14:22 <rjarry> otherwise it would not work at all

14:24 <rjarry> when running /exec -bg 'sleep 5 && echo -e "\a" >&2' from weechat, nothing happens, when running sleep 5 && echo -e "\a" >&2 from outside weechat, the window urgent flag is set

14:25 <dnkl> the urgent flag is only set of the foot window does NOT have keyboard focus

14:26 <rjarry> yep, I added that sleep 5 to have the time to focus to another window

14:26 <dnkl> also make sure no one has emitted the 1042 private mode escape sequence

14:26 <rjarry> the same thing works in other terminals

14:27 <rjarry> hmm, how could I know that ?

14:28 <rjarry> any specific string I could grep?

14:28 <dnkl> I can reproduce. But I can promise you, this is simply because the BEL isn't forwarded to foot. Question is why

14:29 <rjarry> yeah :)

14:30 <rjarry> could it be some ncurses internal thing that parses foot terminfo in a bad way?

14:31 <dnkl> maybe... what does "infocmp | grep bel" return?

14:31 <rjarry> bel=^G

14:31 <rjarry> from outside weechat

14:32 <rjarry> same from inside weechat

14:33 <rjarry> dnkl: for what its worth, the bell is not sent using any terminfo capability, it is using printf("\a") https://github.com/weechat/weechat/blob/master/src/core/wee-command.c#L5233-L5237

14:35 <dnkl> using your echo test from within weechat, I'm NOT seeing urgent being set on any terminal...

14:35 <rjarry> one sec

14:36 <rjarry> ok, forget it, it will not work with /exec

14:37 <rjarry> the thing is /print -beep cannot be delayed

14:40 <dnkl> you can try setting bell.command="notify-send foo bar", and bell. command-focused=yes

14:41 <dnkl> assuming you have a notification daemon running

14:41 <dnkl> otherwise replace with some other command

14:41 <dnkl> this'll let you see if the BEL is received by foot or not

14:43 <rjarry> I can receive the notification when doing /print -beep in weechat with these settings in foot.ini

14:46 <rjarry> dnkl: I didn't find any string that looks remotely similar to a 1042 CSI private escape sequence neither in weechat sources, nor in ncurses

14:47 <dnkl> I did some logging, and don't see why urgent shouldn't be set

14:47 <dnkl> which compositor are you using?

14:47 <rjarry> sway

14:47 <dnkl> makes no sense that it would work outside weechat but not inside

14:47 <rjarry> I know

14:48 <dnkl> foot doesn't know, or care, about which program is currently running...

14:50 <rjarry> by the way I have found a way to send a BEL explicitly and have the time to focus another window

14:50 <rjarry> /print -date +5 -beep

14:50 <rjarry> from weechat

14:51 <rjarry> ah damn, no it does not delay

14:52 <dnkl> which other terminals have you tested?

14:52 <rjarry> alacritty

14:52 <rjarry> I'll test some others

14:52 <dnkl> I was mostly interested in whether they were Wayland or X11

14:53 <dnkl> as urgency is handled completely different

14:53 <rjarry> alacritty should be wayland native

14:55 <rjarry> dnkl: can you ping me here? I started weechat in kitty to check it out

14:55 <dnkl> rjarry: ping

14:56 <rjarry> yep, it sets the urgent flag with kitty as well

14:57 <rjarry> there is one detail (I'm not sure that matters), my foot window is in a sway scratchpad

14:57 <rjarry> i.E. a floating window

14:57 <dnkl> doesn't matter to foot

14:58 <dnkl> foot will use the xdg activation protocol to signal urgency to the compositor

14:58 <dnkl> this is done a long as the window does but have focus

14:58 <dnkl> after that, it's up to the compositor

14:58 <rjarry> yeah, I had followed the patches

14:59 <dnkl> try running foot with WAYLAND_DEBUG=1

14:59 <rjarry> ok

15:00 <rjarry> it is started now

15:01 <rjarry> ping me again?

15:01 <dnkl> see if you get anything related to xdg activation when the window is unfocused

15:01 <dnkl> rjarry: ping

15:05 <rjarry> dnkl: https://0x0.st/oFKF.txt

15:05 <rjarry> maybe you need more context?

15:17 <dnkl> rjarry: so, both inside and outside weechat looks the same. That'd mean it's sway's fault... not that that makes any sense either...

15:18 <rjarry> T_T

15:21 <dnkl> rjarry: try comparing with e.g kitty.. 🤷

15:21 <dnkl> running out of ideas here..

15:45 <rjarry> dnkl: yeah, good idea

15:45 <rjarry> if all fails, I'll resort to gdb, lol

19:41 <rjarry> dnkl: after inspecting the wayland debug logs of alacritty/kitty/foot with weechat running and sending a bell character, I noticed only one difference

19:41 <rjarry> dnkl: foot misses one log line that relates to "xdg_activation" wl_registry@**.global(34, "xdg_activation_v1", 1)

19:42 <rjarry> I have absolutely no idea what is that for

20:32 <rjarry> dnkl: I think I may have found what is different, I run weechat in a floating sway window (scratchpad) when the scratchpad is hidden, the urgent flag is ignored, when it is not displayed but does not have keyboard focus, the urgent flag is honnored by the compositor

20:33 <rjarry> so in the end, it may very well be a wayland/sway issue

20:35 <rjarry> yeah, I just confirmed that with kitty. same behaviour when the scratchpad is hidden

20:46 <rjarry> dnkl: for reference: https://github.com/swaywm/sway/blame/master/sway/tree/view.c#L369-L373