From: storm@cua.dk (Kim F. Storm)
Cc: Chong Yidong <cyd@stupidchicken.com>,
rms@gnu.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: [rudalics@gmx.at: Re: jit lock sit-for provokes redisplay provokes imenu]
Date: Thu, 31 Aug 2006 09:49:00 +0200 [thread overview]
Message-ID: <m3bqq19wgj.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <44F67D80.4010800@gmx.at> (martin rudalics's message of "Thu, 31 Aug 2006 08:11:12 +0200")
martin rudalics <rudalics@gmx.at> writes:
> The buffer changes during scrolling and window resizing, however, are
> considerably more serious since they affect responsiveness of Emacs. My
> Emacs considerably lags behind other applications during scrolling and
> flickers noticeably whenever I drag a modeline. Now consider that for
> every _single_ line dragged or scrolled I call `imenu-update-menubar'.
> The only buffer "change" here is the fontification of one single line.
> That doesn't make any sense. And it makes the speed of scrolling depend
> (1) on the size of the buffer and (2) the quality of a thing like
> `imenu-create-index-function'. Wouldn't it make more sense to spend
> that time to filter out, for example, all those definitions Imenu finds
> in C comments or strings?
And you changes (at the C level + imenu) fixes all these problems, right?
If, so I think we are wasting our time discussing sub-optimal ways to
fix a specific problem where we already have a generic solution.
Can't we just install Martin's patch and get closer to the pretest??
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2006-08-31 7:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 9:52 [rudalics@gmx.at: Re: jit lock sit-for provokes redisplay provokes imenu] Richard Stallman
2006-08-28 10:01 ` David Kastrup
2006-08-28 11:47 ` Kim F. Storm
2006-08-29 17:18 ` Richard Stallman
2006-08-28 16:22 ` Chong Yidong
2006-08-28 16:44 ` Stefan Monnier
2006-08-29 11:47 ` Richard Stallman
2006-08-30 2:43 ` Chong Yidong
2006-08-30 3:41 ` Stefan Monnier
2006-08-30 7:52 ` Kim F. Storm
2006-08-31 0:28 ` Chong Yidong
2006-08-31 4:01 ` Stefan Monnier
2006-08-30 17:59 ` Richard Stallman
2006-08-30 18:29 ` martin rudalics
2006-08-31 0:29 ` Chong Yidong
2006-08-31 6:11 ` martin rudalics
2006-08-31 7:49 ` Kim F. Storm [this message]
2006-08-31 13:12 ` Chong Yidong
2006-08-31 22:57 ` Richard Stallman
2006-09-01 13:42 ` Chong Yidong
2006-08-31 18:16 ` Richard Stallman
2006-09-01 6:41 ` martin rudalics
2006-09-01 12:47 ` Richard Stallman
2006-08-30 20:49 ` Stefan Monnier
2006-08-31 18:16 ` Richard Stallman
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=m3bqq19wgj.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@gnu.org \
/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).