From: Karl Eichwalder <ke@gnu.franken.de>
Cc: kifer@cs.sunysb.edu (Michael Kifer),
traverso@dm.unipi.it, emacs-devel@gnu.org
Subject: Re: ediff feature request: diffing line by line
Date: Sun, 17 Mar 2002 05:04:01 +0100 [thread overview]
Message-ID: <shlmcrvo0e.fsf@tux.gnu.franken.de> (raw)
In-Reply-To: <87bsdof724.fsf@gnu.org> (Alex Schroeder's message of "Sun, 17 Mar 2002 00:04:35 +0100")
Alex Schroeder <alex@gnu.org> writes:
>> Ediff is designed to parse the output of diff and then present it in
>> different ways.
Concerning presentation there isn't that much to change
>> What you are proposing is a kind of "incremental diff", if I
>> understand it correctly. I think it would require a major
>> generalization of the existing code to do that.
Yes, it is kind of "incremental"; let's consider these variants:
->>Everyone in the world is permitted to copy and distribute verbatim copies
^^^^^^^^^^^^
of this license document, but changing it is not allowed.
^^^^
<<-
->>Everyone is permitted to copy and distribute verbatim copies
of the license document, but changing it is not allowed.
~~~
<<-
Ediff sees only 1 difference, and the user may ask for a
`ediff-switch-to-line-mode' option able to make chunks of the hunks:
->>Everyone in the world is permitted to copy and distribute verbatim copies
^^^^^^^^^^^^
<<-->>of this license document, but changing it is not allowed.
^^^^
<<-
->>Everyone is permitted to copy and distribute verbatim copies
<<-->>of the license document, but changing it is not allowed.
~~~
<<-
Of course, this option is useful only as long as we have to compare the
same number of similar lines.
> I'm not sure, as I understand it, all Karl is saying that we would
> like to see more commands to act upon the differences -- copy the
> replace the first word of chunk A with the first word of chunk B and
> show me a new diff output. The diff output -- the underlying calls to
> diff and the processing of the output, and the ediff display need not
> be changed.
Yes, that's the "incremental" aspect of the proposal. Thanks for
clarifying!
--
ke@suse.de (work) / keichwa@gmx.net (home): |
http://www.suse.de/~ke/ | ,__o
Free Translation Project: | _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/ | (*)/'(*)
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-03-17 4:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-16 13:54 ediff feature request: diffing line by line Karl Eichwalder
2002-03-16 16:27 ` Carlo Traverso
2002-03-16 17:43 ` Michael Kifer
2002-03-16 23:04 ` Alex Schroeder
2002-03-17 4:04 ` Karl Eichwalder [this message]
2002-03-17 15:40 ` Andreas Schwab
2002-03-17 16:26 ` Carlo Traverso
2002-03-17 18:37 ` Michael Kifer
2002-03-17 20:41 ` Carlo Traverso
2002-03-17 19:20 ` Richard Stallman
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=shlmcrvo0e.fsf@tux.gnu.franken.de \
--to=ke@gnu.franken.de \
--cc=emacs-devel@gnu.org \
--cc=keichwa@gmx.net \
--cc=kifer@cs.sunysb.edu \
--cc=traverso@dm.unipi.it \
/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).