all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jose Antonio Ortega Ruiz <jaortega@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 6856@debbugs.gnu.org, rfrancoise@debian.org
Subject: bug#6856: 24.0.50; fill-paragraph always marks buffer as modified
Date: Sat, 14 Aug 2010 16:27:38 +0200	[thread overview]
Message-ID: <87d3tlz2ud.fsf@newton.homeunix.net> (raw)
In-Reply-To: <83iq3dth7x.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 14 Aug 2010 17:13:38 +0300")

On Sat, Aug 14 2010, Eli Zaretskii wrote:

>> From: Jose Antonio Ortega Ruiz <jaortega@gmail.com>
>> Date: Sat, 14 Aug 2010 15:50:44 +0200
>> Cc: rfrancoise@debian.org
>> 
>> 1. emacs -Q
>> 2. Open any file, go to a filled paragraph spawning more than 1 line
>> 3. M-q. If the paragraph was already filled, no modification of the
>>    buffer occurs, but the buffer is marked as modified nonetheless.
>> 3'. If the first M-q actually modified the text, save the buffer and go
>>     to 3: a second M-q does not change the text but marks the buffer as
>>     modified.
>
> That's how M-q worked since day one.  It has no way of testing whether
> a paragraph is already filled, so it always refills it, which causes
> the buffer to become modified, because the text is being moved around
> (you just don't see it because text is usually not displayed until
> completely refilled).

Yes, i knew this is not a regression, but was hoping that there was an
easy way to "fix" it. Sounds like there isn't. Thanks for the
clarification.

jao





      reply	other threads:[~2010-08-14 14:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-14 13:50 bug#6856: 24.0.50; fill-paragraph always marks buffer as modified Jose Antonio Ortega Ruiz
2010-08-14 14:13 ` Eli Zaretskii
2010-08-14 14:27   ` Jose Antonio Ortega Ruiz [this message]

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=87d3tlz2ud.fsf@newton.homeunix.net \
    --to=jaortega@gmail.com \
    --cc=6856@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=rfrancoise@debian.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.