From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Ediff: compare two (long) buffers Word-by-word
Date: Tue, 27 Nov 2018 10:16:05 +0200 [thread overview]
Message-ID: <83d0qrgcl6.fsf@gnu.org> (raw)
In-Reply-To: <1543153712.1859.6.camel@gmail.com> (message from ST on Sun, 25 Nov 2018 15:48:32 +0200)
> From: ST <smntov@gmail.com>
> Date: Sun, 25 Nov 2018 15:48:32 +0200
> Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
>
> 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 still am not sure I understand what's wrong with the existing
command ediff-regions-wordwise.
> I assume the performance concerns where relevant 15-20 years ago
> (presumably the time when those lines of the docs were written).
It could be. I removed from the documentation the numbers that
defined "large", however in general, for some value of "large" you
will still see slower performance from wordwise comparison compared to
the linewise comparison.
> 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
Again, why doesn't ediff-regions-wordwise fit the bill?
> If this mailing list is the proper place to ask for enhancements: could
> those two functions(/menu options) be added to Emacs, please?
Bugs and enhancement request should be submitted using
report-emacs-bug, thank you.
next prev parent reply other threads:[~2018-11-27 8:16 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
2018-11-27 8:16 ` Eli Zaretskii [this message]
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=83d0qrgcl6.fsf@gnu.org \
--to=eliz@gnu.org \
--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).