-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Won't move Emacs windows (?) #28
Comments
Guess it's time to switch to vim Hmm, that's very bizarre, not something I've seen or understand. A couple of clarifications: When you say On the second distribute, it still leaves space for this emacs window, right? i.e. if you opened a third window (say You mentioned x11 so I'm assuming there's no wayland involved, but maybe it's that emacs uses something other than |
:) Turns out I'm mostly a Vim person already, however https://notmuchmail.org/ and https://orgmode.org/ are pretty nifty, and https://github.com/emacs-evil/evil makes the whole lot bearable.
Yeah, it's super weird and also hard to describe. I've recorded a video to clarify: slinger-emacs.mp4Here's what's happening in the video:
Yep. I'm not sure whether the same phenomenon occurs with Gnome Shell under Wayland.
Yeah. It just doesn't move the window. I currently have the following extensions enabled: |
As of some version of Gnome Shell 3.38 (3.38.1 maybe? Not sure. I'm now on 3.38.2 with X11, and this is still there.), some parts of Slinger (see below for which) don't seem to properly move my Emacs window any more. The following currently works for me to reproduce the issue:
slinger-move-left
)Curiously,
slinger-move-right
et al appear to work reliably, but Distribute and the Super+A-Menu tend to fail. A freshly-started Emacs doesn't seem to suffer from this (but one "Distribute" appears enough to break it).I'm not sure other apps are affected or what's different/specific about Emacs. Other apps that are on the same desktop as Emacs may also misbehave. There's nothing in the Shell logs. I'm on 2b867b9.
I'm sorry about the fuzzy bug report. This has been annoying me for a while, but the circumstances under which it happens have remained a bit of a mystery.
The text was updated successfully, but these errors were encountered: