all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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:12:13 +0200	[thread overview]
Message-ID: <83efb7gcrm.fsf@gnu.org> (raw)
In-Reply-To: <CAP_d_8Vj+kRXJYQhYuffQJcq3+C_vECjAG0_0vmbzLL6X9FaRQ@mail.gmail.com> (message from Yuri Khan on Sun, 25 Nov 2018 16:17:08 +0700)

> From: Yuri Khan <yurivkhan@gmail.com>
> Date: Sun, 25 Nov 2018 16:17:08 +0700
> Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
> 
> ‘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.

Thanks, I fixed the documentation to be more explicit about what is
being compared by these functions.



  parent reply	other threads:[~2018-11-27  8:12 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
2018-11-27  8:12   ` Eli Zaretskii [this message]
     [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83efb7gcrm.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.
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.