From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Text Properties And Buffer Modification
Date: Wed, 05 Dec 2018 21:09:50 +0200 [thread overview]
Message-ID: <831s6v94e9.fsf@gnu.org> (raw)
In-Reply-To: <5C082139.6060802@gmx.at> (message from martin rudalics on Wed, 05 Dec 2018 20:04:25 +0100)
> Date: Wed, 05 Dec 2018 20:04:25 +0100
> From: martin rudalics <rudalics@gmx.at>
> CC: emacs-devel@gnu.org
>
> >>> Don't forget that the modified status is important for more than
> >>> just saving to a file: it is important for redisplaying the
> >>> buffer, for example.
> >>
> >> Really?
> >
> > Is that a rhetorical question?
>
> I would have thought that buffer redisplay is triggered only by
> bset_redisplay and BUF_COMPUTE_UNCHANGED which IIUC are called the
> same way for overlays and text properties. Am I wrong?
Yes. The display engine sometimes needs to know not only whether the
buffer needs to be redisplayed, but also _why_. Search xdisp.c for
MODIFF, and you will see.
next prev parent reply other threads:[~2018-12-05 19:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 23:39 Text Properties And Buffer Modification T.V Raman
2018-12-05 6:33 ` Eli Zaretskii
2018-12-05 7:15 ` Joost Kremers
2018-12-05 8:30 ` Eli Zaretskii
2018-12-05 15:32 ` Stefan Monnier
2018-12-05 17:35 ` T.V Raman
2018-12-05 18:42 ` Eli Zaretskii
2018-12-05 19:04 ` martin rudalics
2018-12-05 19:09 ` Eli Zaretskii [this message]
2018-12-06 9:07 ` martin rudalics
2018-12-06 9:19 ` Eli Zaretskii
2018-12-06 10:10 ` martin rudalics
2018-12-06 10:28 ` Eli Zaretskii
2018-12-06 18:46 ` martin rudalics
2018-12-06 19:16 ` Eli Zaretskii
2018-12-08 9:42 ` martin rudalics
2018-12-08 11:22 ` Eli Zaretskii
2018-12-05 20:54 ` Stefan Monnier
2018-12-06 6:04 ` Eli Zaretskii
2018-12-05 9:16 ` martin rudalics
2018-12-05 10:54 ` Eli Zaretskii
2018-12-05 19:04 ` martin rudalics
2018-12-05 19:08 ` Eli Zaretskii
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=831s6v94e9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rudalics@gmx.at \
/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).