From: martin rudalics <rudalics@gmx.at>
Cc: Chong Yidong <cyd@stupidchicken.com>,
monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: [rudalics@gmx.at: Re: jit lock sit-for provokes redisplay provokes imenu]
Date: Wed, 30 Aug 2006 20:29:40 +0200 [thread overview]
Message-ID: <44F5D914.3020604@gmx.at> (raw)
In-Reply-To: <E1GIULW-0000NH-V1@fencepost.gnu.org>
> Stefan wrote:
>
> This only eliminates one particular source of unwanted updates. I don't
> think this code is worth the trouble.
>
> That cause of unwanted updates is the only one we know of. Nothing
> else is likely to change the buffer in the background.
`jit-lock-fontify-now' during scrolling, searching, window resizing.
Not mentioning the plethora of "hidden buffer changes" in c-mode.
> Better yet, introduce a macro `with-buffer-unmodified' like the one used in
> jit-lock, and make it manage a `buffer-really-modified-tick', kind of like
> the buffer-chars-modified-tick. Then use it in jit-lock/font-lock
> and friends.
>
> That seems a lot more trouble, and I don't see that it is needed.
I think it is needed.
next prev parent reply other threads:[~2006-08-30 18:29 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 [this message]
2006-08-31 0:29 ` Chong Yidong
2006-08-31 6:11 ` martin rudalics
2006-08-31 7:49 ` Kim F. Storm
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=44F5D914.3020604@gmx.at \
--to=rudalics@gmx.at \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).