You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i3 centers new floating windows by default. Except for Emacs frames. Those are stuck to the top left. I've triple checked the emacs docs and my dotemacs, and as far as I can tell, this should not be happening.
To be more specific, the default-frame-alist variable contains default parameters for new frames. It does not contain the keys top or left in my config. According to the emacs docs, this should cause the window manager to do whatever it does by default.
To test this yourself, put this in your .i3/config:
Edit: Here's a log file of me reproducing the observed behaviour. It's probably much longer than necessary, but a search for "personal-org" will get you to where the interesting bits happen.
I have not changed my config. I have not updated i3. But it works just fine now. I have absolutely no idea what might be at fault... Interesting. I'll close this issue, since I'm no longer able to reproduce.
i3faq post for reference: https://faq.i3wm.org/question/6314/floating-emacs-frames-arent-centered/
i3 centers new floating windows by default. Except for Emacs frames. Those are stuck to the top left. I've triple checked the emacs docs and my dotemacs, and as far as I can tell, this should not be happening.
To be more specific, the
default-frame-alist
variable contains default parameters for new frames. It does not contain the keystop
orleft
in my config. According to the emacs docs, this should cause the window manager to do whatever it does by default.To test this yourself, put this in your
.i3/config
:And try:
Or maybe:
Edit: Here's a log file of me reproducing the observed behaviour. It's probably much longer than necessary, but a search for "personal-org" will get you to where the interesting bits happen.
http://logs.i3wm.org/logs/5742636757417984.bz2
The text was updated successfully, but these errors were encountered: