From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: ediff on Win32
Date: Fri, 09 Feb 2007 08:16:04 +0100 [thread overview]
Message-ID: <45CC1FB4.1010201@gmail.com> (raw)
In-Reply-To: <Xns98D255662406wssddcgisnet@208.49.80.252>
Bob Babcock wrote:
> I tried diff3.exe from two sources:
> http://www.tasoft.com/patches.html
> http://sourceforge.net/projects/gnuwin32/
> but neither works. Only change is that if I run ediff-documentation and
> kill the process tree, I actually get the documentation instead of an error
> message (in emacs 21.3.1).
The one from gnuwin32 is what is shipped with Emacs+EmacsW32 (which
contains the yet in beta-test Emacs v 22) and I have had no problems
with it.
next prev parent reply other threads:[~2007-02-09 7:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 5:19 ediff on Win32 Bob Babcock
2007-02-08 8:14 ` Kevin Rodgers
[not found] ` <mailman.4166.1170922499.2155.help-gnu-emacs@gnu.org>
2007-02-09 5:31 ` Bob Babcock
2007-02-09 7:16 ` Lennart Borgman (gmail) [this message]
2007-02-09 16:08 ` Eli Zaretskii
[not found] ` <mailman.4236.1171037300.2155.help-gnu-emacs@gnu.org>
2007-02-09 18:15 ` Bob Babcock
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=45CC1FB4.1010201@gmail.com \
--to=lennart.borgman@gmail.com \
--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).