-
-
Notifications
You must be signed in to change notification settings - Fork 186
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
Flickering/flashing while scrolling #314
Comments
I'm also seeing this when it's built without xwidgets support, FWIW. |
Hey @dabrahams , I suspect, it might be partially related to #137. One of the suggestions - give Emacs 28a try (e.g. As for Emacs Mac Port, Mitsuharu Yamamoto worked hard on the rendering side and did amazing job for it to look nice. I could 'extract' this into And now my curiousity wins. I want to know why you decided to give |
Hi Boris,
I was directed to emacs-plus by the getting-started guide for doom emacs,
which has some (seemingly outdated
<doomemacs/doomemacs#4663>) things to say about
multi-tty support weaknesses in emacs-mac. The one other thing that's
attractive to me about emacs-plus is xwidgets support, which I might use if
I start reading my mail with emacs again (there's way too much HTML email
out there to live without it).
I could try emacs-plus@28; that might be interesting.
…On Tue, Feb 16, 2021 at 10:59 PM Boris Buliga ***@***.***> wrote:
Hey @dabrahams <https://github.com/dabrahams> ,
I suspect, it might be partially related to #137
<#137>. One of
the suggestions - give Emacs 28a try (e.g. brew install ***@***.***). I
haven't see any glitches for a while on the master branch.
As for Emacs Mac Port, Mitsuharu Yamamoto worked hard on the rendering
side and did amazing job for it to look nice. I could 'extract' this into
emacs-plus, but then it would contradict with emacs-plus goal to be a
formula for GNU Emacs and stay as close as possible. Emacs Mac Port is not
just a formula for brew, it's GNU Emacs with a huge amount of patches for
macOS.
And now my curiousity wins. I want to know why you decided to give
emacs-plus a try. 😄 Don't get me wrong, I am happy that you did and I am
sad that you are getting these glitches, but I haven't used Emacs Mac Port
for years and don't know how people feel about it 😄
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#314 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAKYIJVWMIC3MYF3CYBZZTS7NSNFANCNFSM4XVNX4EA>
.
--
-Dave
|
Indeed, I haven't seen any issues in Emacs 28 in a while. Seems like it was fixed. Not using Emacs 27 for a long time, so can't say for sure the state of this issue there.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
…On Friday, April 2nd, 2021 at 18:18, kohlworks ***@***.***> wrote:
I was seeing this behavior on ***@***.*** multiple times a day (macOS Catalina + doom emacs). I recently switched to ***@***.*** --with-native-comp. Could bring other issues but no more flickering/flashing, which is absolutely lovely. Definitely 'feels' snappier, fwiw.
Thank you for your work ***@***.***(https://github.com/d12frosted).
—
You are receiving this because you were mentioned.
Reply to this email directly, [view it on GitHub](#314 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ABRU3CPLPMIK7DYHG23MLYTTGXN33ANCNFSM4XVNX4EA).
|
Quick note to verify that I too have seen zero flickering issues with Emacs 28, albeit on the |
Unfortunately, while Emacs 28 had fixed this issue, at least for me, it's back on Emacs 29.1 :(. It really destroys the experience... however, I noticed that this only happens on my Macbook Air, but not on my Mac Pro M1... even though I installed both via brew in the exactly same way. |
I'm experiencing the effect described here: syl20bnr/spacemacs#12009
I'm on Big Sur; emacs-plus was installed with
brew install emacs-plus --with-mailutils --with-xwidgets
I never have this problem with the emacs-mac-port, which I used happily for years before trying emacs-plus.
The text was updated successfully, but these errors were encountered: