Chris Feng

No idea yet but EXWM creates a frame for every new floating X window and this may trigger persp-mode to manipulate window configurations.

> it would be cool if winner mode can restore floating windows layout. I totally agree with this, but not through workarounds.

Probably nothing to do with the application itself. I tried it myself and it behaved normally. How do you get the buffer read-only error? I guess other applications should also...

@emiljoha > I am having a similar problem where the Firefox buffer occasionally becomes read only and I have to kill it and start it again. What if you hide...

@emiljoha Did you manage to get a debug log?

@sarg Thanks for the log. It seemed for some reason `exwm-input--on-buffer-list-update` ignored the event. Could you insert a log into the function just like the following? ```elisp (defun exwm-input--on-buffer-list-update ()...

> What I see is that `exwm-input--on-buffer-list-update` isn't called at all. Can't find it in the log either. Was the buffer killed normally? Otherwise I can't see why the hook...

@emiljoha Unfortunately I was not able to reproduce the problem according to your recipe. Nevertheless I found a case where a `*temp*` buffer can cause the problem. I've pushed a...

@TsarFox From your debug log I noticed the input focus always stayed on Firefox so this is a different issue and perhaps caused by some unusual config. But anyway: *...

@TsarFox Perhaps you had them working in char-mode? What if putting them in line-mode and avoiding switching window with global keys?