Miroslav Koškár

I would suggest to change `/input set_unread_current_buffer` such that it would place read marker after last visible line at the bottom of the current window and scroll one line to...

I've tested this with latest ``-git`` version. There is no longer the crosshair thingy so I've tested with ``crosshair`` shader. My laptop screen is 1600x900. 1) I start at left...

I see, well this was just something I've come across and it is edge case, though I thought easily fixed. Otherwise it doesn't affect me really and if it requires...

> Aah, finally, I knew there must be somebody still using X screens :). Haha, yeah, I'm kinda playing with zaphod mode (multiple separate X screens). > Right now, not...

No problem ;) > Though, I still feel like maybe DISPLAY=:1.0 should just touch screen 0, whereas DISPLAY=:1 should touch all of them. When screen number is omitted (e.g., :1)...

Same issue here, tested with `xmonad`, `i3`, and `openbox`. While removing `xwindow` module seemingly fixes handling of urgency events, it's not really sensible workaround because `xwindow` is somewhat essential.

This is partially fixing #552.

@weechatter I was actually thinking about it, but then it seemed lot more work and maybe really needless duplication? I mean you can still use ``/window scroll`` separately before placing...

@jvoisin right, it will get more pronounced with slow connection @fguillot aha, yeah embedding it in every response seems ... well last resort I guess, at that point probably having...