unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: [rudalics@gmx.at: Re: jit lock sit-for provokes redisplay provokes imenu]
Date: Wed, 30 Aug 2006 20:28:00 -0400	[thread overview]
Message-ID: <871wqxlpf3.fsf@furball.mit.edu> (raw)
In-Reply-To: <jwv4pvuc2yi.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 29 Aug 2006 23:41:19 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> 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.

I don't see how this could possibly work.  We can't update
buffer-really-modified-tick in Lisp code for arbitrary buffer changes
(that's the whole point of Martin's patch --- you have to do it at the
C level).  And you can't use it to manage a general-purpose variable
like imenu-menubar-modified-tick, because that keeps track of the
value of (buffer-modified-tick) as of the last call to
`imenu-update-menubar', so imenu must reset
imenu-menubar-modified-tick during each call to
`imenu-update-menubar'.

  parent reply	other threads:[~2006-08-31  0:28 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 [this message]
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
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=871wqxlpf3.fsf@furball.mit.edu \
    --to=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --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).