all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Samuel Wales <samologist@gmail.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>, 47505@debbugs.gnu.org
Subject: bug#47505: 25.1; ediff thinks words changed when filling prefixed
Date: Thu, 01 Apr 2021 02:17:18 +0200	[thread overview]
Message-ID: <8735wa504x.fsf@web.de> (raw)
In-Reply-To: <CAJcAo8t1HTuySkkHU65c2ALX1vKPmLBkVGCHAoniQ0j3CQAD4w@mail.gmail.com> (Samuel Wales's message of "Wed, 31 Mar 2021 17:04:36 -0700")

Samuel Wales <samologist@gmail.com> writes:

> i don't know.  i just know what seems right and seems wrong.  not too
> useful is it?  but it is better than not filing the bug perhaps.
>
> diff-mode does it right so ediff can.  filladapt can intuit prefixes.
> comment syntaxes are known.  somewhere in there lies a fix maybe.
>
> commented paragraphs in org/shell/elisp style are always commented at
> bol.  idk what diff-mode does.

I don't know how diff-mode does it, but I wonder if it then doesn't sort
out changes that are significant.  "I don't know" is not meant ironic,
maybe someone else can help further.

Regards,

Michael.





  reply	other threads:[~2021-04-01  0:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87a6p5qumw.fsf@gnus.org>
2021-03-30 22:02 ` bug#47505: 25.1; ediff thinks words changed when filling prefixed Samuel Wales
2021-03-31  7:25   ` Andreas Schwab
2021-03-31 19:28     ` Samuel Wales
2021-03-31 23:53       ` Michael Heerdegen
2021-04-01  0:04         ` Samuel Wales
2021-04-01  0:17           ` Michael Heerdegen [this message]
2021-05-08 12:26         ` Lars Ingebrigtsen
2021-05-08 20:42           ` Samuel Wales
2021-03-31 19:30     ` Samuel Wales
     [not found]   ` <handler.47505.C.162047678518512.notifdonectrl.0@debbugs.gnu.org>
2021-05-08 20:40     ` bug#47505: acknowledged by developer (control message for bug #47505) Samuel Wales

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=8735wa504x.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=47505@debbugs.gnu.org \
    --cc=samologist@gmail.com \
    --cc=schwab@linux-m68k.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.