From: "B. T. Raven" <btraven@nihilo.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Ediff: compare two (long) buffers Word-by-word
Date: Sat, 24 Nov 2018 16:26:44 -0600 [thread overview]
Message-ID: <ptcj6u09eu@news1.newsguy.com> (raw)
In-Reply-To: <mailman.4546.1543093349.1284.help-gnu-emacs@gnu.org>
On 11/24/2018 1:33 PM, ST wrote:
> Hello,
>
> I use Emacs 26.1 and try to compare two (long) buffers (opened side by
> side) by clicking Tools -> Compare (Ediff) -> Windows Word-by-word...
> Then I choose both Windows (A and B) by clicking on each opened buffer.
> However it looks like Emacs compares only the visible parts of the two
> buffers, not the whole buffers. Why?
If you display the same buffer in 2 windows and then scroll one window
past what is displayed in the other window, ediff-windows-wordwise
doesn't find any differences. I've never used it before and I don't know
what it's usefulness might be. It must be some kind of
short-cut for ediff-buffers used with only 2 buffers.
> I saw there is a command `ediff-windows-wordwise`... How is "Window"
> defined? - as "currently visible part of a buffer"? If yes, is there
> something like `ediff-buffers-wordwise`?
A window is just the non-overlapping screen area where a buffer is
displayed.
Type C-h f ediff- tab tab and you'll see all the ediff functions.
ediff-buffers is probably the one you want. It can also be accessed from
the menu.
>
> I have `git` in `exec-path`, so maybe I can make ediff to display the
> output of `git diff --word-diff file1 file2` in ediff style?
Probably; M-! will let you enter a shell command.
>
> https://emacs.stackexchange.com/questions/46161/ediff-compare-two-long-buffers-word-by-word
>
> Thank you!
>
>
Ed
next parent reply other threads:[~2018-11-24 22:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4546.1543093349.1284.help-gnu-emacs@gnu.org>
2018-11-24 22:26 ` B. T. Raven [this message]
2018-11-24 19:33 Ediff: compare two (long) buffers Word-by-word ST
2018-11-24 23:35 ` Oleg Cherkasov
2018-11-25 9:17 ` Yuri Khan
2018-11-25 13:48 ` ST
2018-11-27 8:16 ` Eli Zaretskii
2018-11-27 8:12 ` Eli Zaretskii
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=ptcj6u09eu@news1.newsguy.com \
--to=btraven@nihilo.net \
--cc=help-gnu-emacs@gnu.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.
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).