unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Yuan Fu <casouri@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: 59481@debbugs.gnu.org
Subject: bug#59481: 29.0.50; c-ts-mode doesn't play nicely with  pixel-scroll-precision-mode
Date: Tue, 22 Nov 2022 12:44:18 -0800	[thread overview]
Message-ID: <6B7338DA-2F7A-486B-8213-B180D1BA146E@gmail.com> (raw)
In-Reply-To: <877czn3zn5.fsf@yahoo.com>


Po Lu <luangruo@yahoo.com> writes:

> Enable pixel-scroll-precision-mode, then open src/xterm.c.  Go to line
> 3439, enable c-ts-mode, and scroll up _with a trackpad_ until line 1675
> becomes visible near the start of the window.  Finally, go down to line
> 1817: brackets will become randomly fontified in the error face.
>
> In addition, I was expecting c-ts-mode to be quite a lot faster
> fontifying during precision scrolling, but it is currently as slow as CC
> Mode.  I think that is almost definitely a bug somewhere in our
> tree-sitter fontification code, since emacs-lisp-mode fontifies much
> faster.

How do you decide if the scrolling is fast or not? Maybe you are seeing
palpable lags? I’m using macOS with the builtin trackpad, and scrolling
is pretty snappy. Maybe this only happens on Linux? I’m also seeing
random error faces (albeit not on brackets), could this relate to some
particular way pixel-scrolling works? Does pixel-scrolling do anything
special comparing to normal scrolling when fontifying text?

Thanks,
Yuan





  reply	other threads:[~2022-11-22 20:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <877czn3zn5.fsf.ref@yahoo.com>
2022-11-22 13:08 ` bug#59481: 29.0.50; c-ts-mode doesn't play nicely with pixel-scroll-precision-mode Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-22 20:44   ` Yuan Fu [this message]
2022-11-23  0:45     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6B7338DA-2F7A-486B-8213-B180D1BA146E@gmail.com \
    --to=casouri@gmail.com \
    --cc=59481@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).