From: Joost Kremers <joostkremers@fastmail.fm>
To: help-gnu-emacs@gnu.org
Subject: Re: when nothing happens, buffer still marked as modified
Date: Wed, 05 Dec 2018 16:00:15 +0100 [thread overview]
Message-ID: <877egot3wg.fsf@fastmail.fm> (raw)
In-Reply-To: <83lg548cjz.fsf@gnu.org>
On Wed, Dec 05 2018, Eli Zaretskii wrote:
>> From: Emanuel Berg <moasenwood@zoho.eu>
>> Date: Wed, 05 Dec 2018 11:09:24 +0100
>>
>> Eli Zaretskii wrote:
>>
>> >> But how do I determine if the buffer has
>> >> changed or not? If it has, of course it
>> >> should be marked `**'!
>> >
>> > That's the same problem that M-q has, and it
>> > leaves the modified status intact. Why not do
>> > as it does?
>>
>> I'm not following, "Why not do as it does"?
>
> I mean why not follow M-q's example? It marks the buffer
> modified
> even if re-filling the text arrived at the same text as before
> the
> command.
Now I'm confused. The NEWS section for Emacs 26 says:
** 'fill-paragraph' no longer marks the buffer as changed unless
it
actually changed something.
Which seems to be implemented (correct me if I'm wrong, I only
took a very quick look) by using `buffer-hash'. I thought that was
what you meant when you said "do as it does"...
--
Joost Kremers
Life has its moments
next prev parent reply other threads:[~2018-12-05 15:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 2:48 when nothing happens, buffer still marked as modified Emanuel Berg
2018-12-05 6:55 ` Eli Zaretskii
[not found] ` <mailman.5189.1543993692.1284.help-gnu-emacs@gnu.org>
2018-12-05 7:23 ` Emanuel Berg
2018-12-05 8:22 ` Eli Zaretskii
[not found] ` <mailman.5196.1543998171.1284.help-gnu-emacs@gnu.org>
2018-12-05 10:09 ` Emanuel Berg
2018-12-05 10:58 ` Eli Zaretskii
2018-12-05 13:39 ` Amin Bandali
2018-12-05 13:57 ` Eli Zaretskii
2018-12-05 15:00 ` Joost Kremers [this message]
2018-12-05 17:54 ` Eli Zaretskii
2018-12-05 18:35 ` Michael Heerdegen
[not found] ` <mailman.5239.1544035085.1284.help-gnu-emacs@gnu.org>
2018-12-06 0:49 ` Emanuel Berg
2018-12-05 11:58 ` Michael Heerdegen
[not found] ` <mailman.5204.1544007548.1284.help-gnu-emacs@gnu.org>
2018-12-06 0:47 ` Emanuel Berg
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=877egot3wg.fsf@fastmail.fm \
--to=joostkremers@fastmail.fm \
--cc=help-gnu-emacs@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.