-
Notifications
You must be signed in to change notification settings - Fork 44
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
Ement scrolls image buffers upon insertion of new events #58
Comments
That seems very strange. Ement should not be affecting any buffers other than its own. I'd guess that this is either a problem in your Emacs configuration, or some kind of unusual bug in Emacs related to images. Please try to reproduce in a clean Emacs config (e.g. using |
I wish it was something to do with my config, but alas. I was able to reproduce in a clean config just after the Emacs 28 branch was cut but nevertheless, I will try to reproduce in Emacs 28. As for my sysinfo, here's what M-x report-emacs-bug has to say:
|
I used with-emacs.sh with init.el here to install ement and plz using straight.el. Reproducing this issue is straightforward,
AFAICT, if you send a message in a room, this does not reproduce. Someone else has to send a message. As for sysinfo, this is what M-x report-emacs-bug says: https://gist.github.com/vizs/7a601037d7c99498dd9f2aabda8812e3 |
So you originally encountered this problem when using Emacs from the version-29 (i.e. master) branch? If so, that is crucial information that you must not leave out of a bug report like this. You're running bleeding-edge, unreleased software that may contain new bugs that are unrelated to this package. In your latest comment, you report the problem in Emacs 28, but neither Emacs 28 nor 29 are released yet. Please try to reproduce this bug with a released version of Emacs. You may have discovered a bug in Emacs 28+ that needs to be fixed in Emacs. |
FWIW, I'm unable to reproduce this problem in Emacs 28.0.92. I opened an image in a buffer, zoomed in so it more than filled the window, scrolled down in that window, then opened a room buffer and buried it, then sent messages to that room from another account, and the image did not move. |
Sorry for the late reply, I'm busy with my sem finals, I hope to get back to this bug report on May. But I vaguely remember not being able to reproduce this issue if I posted a message from an alt account in element... but if someone else sends a message, I can reproduce it reliably. |
I don't understand how that could be possible. The software doesn't know that both accounts belong to you, so to it, your alt account is "someone else." |
@Vizs IIRC I saw you mention this in #emacs:matrix.org the other day, that it doesn't only happen when using Ement. So is this confirmed to not be a bug in Ement now? |
It was more like a random observation from time to time even without Ement connected. So I guess it was something more related to Emacs than Ement. But I haven't observed it for quite some time now, I would close the issue. |
For future readers, https://debbugs.gnu.org/cgi/bugreport.cgi?bug=56008 |
Wow, that was quite an involved bug. Thanks to you, Lars, and Eli for working on the fix. |
I apologise right away for this vague report. I tried to investigate to be more specific, only to be unsuccessful.
If you have ement connected and have a room buffer opened (but not viewed anywhere), and the current buffer is a pdf-tools buffer [*], upon insertion of new events in the ement room buffer, the pdf buffer is scrolled. This behaviour is not exhibited by "regular" buffers, as in buffers that only show text. I have been unsuccessful so far in coming up with a reproducer but it goes like this:
[*] I'm using pdf-tools in my description but I observe it in doc-view as well, or even an image-mode buffer with the image inserted such that it can be scrolled (i.e., "s b + +").
Edebug so far has not been very helpful... And nothing unusual shows up in lossage.
EDIT: In my tests, I had to scroll up in the image before (C-v). Ement scrolls down when there's an event. I haven't observed the inverse so far.
The text was updated successfully, but these errors were encountered: