From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
Samuel Wales <samologist@gmail.com>,
47505@debbugs.gnu.org
Subject: bug#47505: 25.1; ediff thinks words changed when filling prefixed
Date: Sat, 08 May 2021 14:26:09 +0200 [thread overview]
Message-ID: <87bl9lqun2.fsf@gnus.org> (raw)
In-Reply-To: <87wntm6ftt.fsf@web.de> (Michael Heerdegen's message of "Thu, 01 Apr 2021 01:53:02 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Depends on what you think what "fine diffs" are. They are actually word
> wise diffs, and comment starts are a just a word. That how it's
> implemented. In the case you describe I find that sometimes annoying,
> too. But I guess it's not easy to change that.
I think this is basically working as intended (even if it's different in
the two cases, because the interfaces emphasise different things).
So I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-05-08 12:26 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
2021-05-08 12:26 ` Lars Ingebrigtsen [this message]
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
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=87bl9lqun2.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=47505@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--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 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).