From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: ttn@glug.org, user42@zip.com.au, emacs-devel@gnu.org
Subject: Re: makeinfo-info.el - use Info-mode with makeinfo-buffer
Date: Wed, 4 Dec 2002 16:23:09 +0200 (IST) [thread overview]
Message-ID: <Pine.SUN.3.91.1021204162148.5872A-100000@is> (raw)
In-Reply-To: <buoadjmthpb.fsf@mcspd15.ucom.lsi.nec.co.jp>
On 4 Dec 2002, Miles Bader wrote:
> > The only problem with this solution is that breaking a line into a list
> > of words is non-trivial due to m17n considerations, especially if the
> > buffer mixes several character sets. IIRC, for that reason, Ediff uses
> > some ad-hoc method instead of relying on syntax categories of characters.
>
> That's OK; for the purpose Richard was asking about, the main thing is
> that it ignores (or rather, de-emphasizes) whitespace-only changes,
> which should work fine even if word-splitting isn't exactly `correct.'
Right. We are left with the task of defining what is white space (not
entirely trivial, as we saw in recent discussions here), but that is much
easier than what Ediff needs to do.
next prev parent reply other threads:[~2002-12-04 14:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87adka7747.fsf@zip.com.au>
[not found] ` <E18Ddmd-0007x2-00@fencepost.gnu.org>
2002-11-29 23:21 ` makeinfo-info.el - use Info-mode with makeinfo-buffer Kevin Ryde
2002-11-30 6:35 ` Thien-Thi Nguyen
2002-12-02 5:56 ` Eli Zaretskii
2002-12-02 6:08 ` Miles Bader
2002-12-02 6:25 ` Eli Zaretskii
2002-12-02 20:54 ` Kevin Ryde
2002-12-03 14:58 ` Richard Stallman
2002-12-04 1:37 ` Miles Bader
2002-12-04 6:07 ` Eli Zaretskii
2002-12-04 6:35 ` Miles Bader
2002-12-04 14:23 ` Eli Zaretskii [this message]
2002-12-04 19:19 ` David Masterson
2002-12-04 20:00 ` Miles Bader
2002-12-02 16:02 ` Stefan Monnier
2002-12-02 17:21 ` 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=Pine.SUN.3.91.1021204162148.5872A-100000@is \
--to=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=ttn@glug.org \
--cc=user42@zip.com.au \
/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).