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 01:53:02 +0200 [thread overview]
Message-ID: <87wntm6ftt.fsf@web.de> (raw)
In-Reply-To: <CAJcAo8vtvv__pw6Gx9VbKfStuKzP05GhJZ2MVF7f=VV2EPhNdQ@mail.gmail.com> (Samuel Wales's message of "Wed, 31 Mar 2021 12:28:52 -0700")
Samuel Wales <samologist@gmail.com> writes:
> doyou think diff's behavior is a bug then? i choose ediff's.
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.
It might be possible to tell Ediff to ignore certain words (like comment
starts) but it's then not trivial to decide whether some text got
commented that was not commented before.
This is all not trivial. There can be lines that are partly code and
partly comment; in Elisp, the comment start can have changed (e.g. ;; ->
;;;), you can have "doubled comments" like ;;; ;;; where uncommenting
would leave comments ... how would you define when two regions
should count as similar?
Regards,
Michael.
next prev parent reply other threads:[~2021-03-31 23:53 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 [this message]
2021-04-01 0:04 ` Samuel Wales
2021-04-01 0:17 ` Michael Heerdegen
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=87wntm6ftt.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.