unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kevin Rodgers <kevin.d.rodgers@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: How do I make ediff-buffers3 ignore whitespace?
Date: Wed, 02 Feb 2011 23:44:24 -0700	[thread overview]
Message-ID: <iidirc$sfn$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTimxjXMN=F0KiFzcA+CoNx+a81vmYDoq2Z91UO2w@mail.gmail.com>

On 2/2/11 8:30 AM, Lennart Borgman wrote:
> I am unable to fix that. Can someone explain exactly how to do it?
> (There may be a bug in some w32 tool involved, I am not sure.)

Is is different than the way to make ediff-buffers ignore whitespace?

(setq ediff-diff-options "-w")

-- 
Kevin Rodgers
Denver, Colorado, USA




  reply	other threads:[~2011-02-03  6:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02 15:30 How do I make ediff-buffers3 ignore whitespace? Lennart Borgman
2011-02-03  6:44 ` Kevin Rodgers [this message]
2011-02-03 12:13   ` Lennart Borgman

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='iidirc$sfn$1@dough.gmane.org' \
    --to=kevin.d.rodgers@gmail.com \
    --cc=emacs-devel@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 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).