From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: jit lock sit-for provokes redisplay provokes imenu
Date: Mon, 24 Jul 2006 10:42:03 -0400 [thread overview]
Message-ID: <E1G51dD-00081T-9m@fencepost.gnu.org> (raw)
In-Reply-To: <44C1E94C.5040806@gmx.at> (message from martin rudalics on Sat, 22 Jul 2006 11:01:00 +0200)
> other words, suppose we have a thing called CHAR_MODIFF: Would we have
> to support the invariant
>
> MODIFF >= CHAR_MODIFF >= SAVE_MODIFF
>
> Yes, that is the idea.
But now I'm in doubt whether I reasoned correctly. It would mean that
when I save a buffer and thusly update save_modiff I'd have to update
char_modiff as well to preserve that invariant.
That is true.
We could drop the requirement thaht CHAR_MODIFF be >= SAVE_MODIFF.
That would be fine, for imenu. Is there another use which
needs to compare those two values?
next prev parent reply other threads:[~2006-07-24 14:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <81CCA6588E60BB42BE68BD029ED4826008838221@wimex2.wim.midas-kapiti.com>
2006-07-20 18:16 ` jit lock sit-for provokes redisplay provokes imenu Richard Stallman
2006-07-20 19:47 ` Drew Adams
2006-07-20 22:41 ` Richard Stallman
2006-07-21 9:13 ` martin rudalics
2006-07-21 19:37 ` Richard Stallman
2006-07-22 9:01 ` martin rudalics
2006-07-24 14:42 ` Richard Stallman [this message]
2006-07-26 9:32 ` martin rudalics
2006-07-21 14:53 ` martin rudalics
2006-07-22 4:38 ` Richard Stallman
2006-07-22 9:21 ` martin rudalics
2006-07-23 7:55 ` martin rudalics
2006-07-24 14:42 ` Richard Stallman
2006-07-26 11:24 ` martin rudalics
2006-07-26 15:10 ` Stefan Monnier
2006-07-26 16:16 ` martin rudalics
2006-07-27 14:35 ` Stefan Monnier
2006-07-26 22:34 ` Richard Stallman
2006-07-26 22:48 ` David Kastrup
2006-07-27 16:04 ` Richard Stallman
2006-07-27 16:27 ` David Kastrup
2006-07-27 23:45 ` Richard Stallman
2006-08-03 9:35 ` martin rudalics
2006-08-20 14:28 ` Chong Yidong
2006-08-21 14:20 ` Kim F. Storm
2006-08-21 15:20 ` Chong Yidong
2006-08-23 15:04 ` Kim F. Storm
2006-07-26 14:51 Marshall, Simon
2006-07-26 15:48 ` martin rudalics
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1G51dD-00081T-9m@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.