From: ST <smntov@gmail.com>
To: Yuri Khan <yurivkhan@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Ediff: compare two (long) buffers Word-by-word
Date: Sun, 25 Nov 2018 15:48:32 +0200 [thread overview]
Message-ID: <1543153712.1859.6.camel@gmail.com> (raw)
In-Reply-To: <CAP_d_8Vj+kRXJYQhYuffQJcq3+C_vECjAG0_0vmbzLL6X9FaRQ@mail.gmail.com>
On Sun, 2018-11-25 at 16:17 +0700, Yuri Khan wrote:
> On Sun, Nov 25, 2018 at 4:02 AM ST <smntov@gmail.com> wrote:
>
> > 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?
> >
> > 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`?
>
> ‘ediff-windows-wordwise’ calls ‘ediff-windows’ which calls
> ‘ediff-regions-internal’, passing to it the two chosen windows and
> their respective visible parts. ‘ediff-windows-linewise’ behaves the
> same way.
>
> This is not documented in their docstrings nor in Info. Moreover,
> (info "(ediff) Major Entry Points") contains the following wording:
>
> > The commands ‘ediff-windows-wordwise’
> > and ‘ediff-regions-wordwise’ are intended for relatively small segments
> > of buffers (e.g., up to 100 lines, depending on the speed of your
> > machine)
>
> which suggests that ‘ediff-windows-*’ should work for 100-line
> fragments, and that will only fit in a visible part of a window with a
> very small font.
>
> There is no command ‘ediff-buffers-wordwise’; maybe this is because of
> performance concerns. You can compare buffers using
> ‘ediff-regions-wordwise’; after you specify two buffers, it will ask
> you to select a region and press C-M-c to proceed, in each buffer.
Somebody has provided a solution which seems to work very good without
any performance issues. There is a small error message, though...
https://emacs.stackexchange.com/questions/46161/ediff-compare-two-long-buffers-word-by-word
I assume the performance concerns where relevant 15-20 years ago
(presumably the time when those lines of the docs were written).
If it is easier, then comparing two files word-by-word, would also be a
nice feature:
https://emacs.stackexchange.com/questions/46206/ediff-compare-two-files-word-by-word
If this mailing list is the proper place to ask for enhancements: could
those two functions(/menu options) be added to Emacs, please?
Thank you!
next prev parent reply other threads:[~2018-11-25 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2018-11-27 8:16 ` Eli Zaretskii
2018-11-27 8:12 ` Eli Zaretskii
[not found] <mailman.4546.1543093349.1284.help-gnu-emacs@gnu.org>
2018-11-24 22:26 ` B. T. Raven
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=1543153712.1859.6.camel@gmail.com \
--to=smntov@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=yurivkhan@gmail.com \
/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).