From: Bob Babcock <wssddc@nospam.gis.net>
To: help-gnu-emacs@gnu.org
Subject: Re: ediff on Win32
Date: Thu, 08 Feb 2007 21:31:29 -0800 [thread overview]
Message-ID: <Xns98D255662406wssddcgisnet@208.49.80.252> (raw)
In-Reply-To: mailman.4166.1170922499.2155.help-gnu-emacs@gnu.org
Kevin Rodgers <kevin.d.rodgers@gmail.com> wrote in
news:mailman.4166.1170922499.2155.help-gnu-emacs@gnu.org:
> Stick with -q for now, just to simplify debugging the problem.
>
> How do you load ediff? Try using --debug-init as well as -q,
> or `M-x set-variable RET debug-on-error RET t RET' after you've
> started emacs, and post the resulting *Backtrace* buffer.
Thanks for your suggestions. Emacs starts cmdproxy.exe when ediff is
started. If I use task manager to kill the process tree for cmdproxy
(killing just the process isn't enough), emacs 21 comes back to life (emacs
22 does not). Then in the backtrace buffer, I see
(file-error "Searching for program" "no such file or directory" "diff3")
I didn't have diff3.exe in my emacs install directory (or anywhere else).
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).
So I'm not sure if I just need a compatible diff3.exe or if something else
is wrong.
When I shutdown for the night after my earlier posting, I had a dozen
messages about cmdproxy not responding. That was a not-very-subtle clue.
next prev parent reply other threads:[~2007-02-09 5:31 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 [this message]
2007-02-09 7:16 ` Lennart Borgman (gmail)
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=Xns98D255662406wssddcgisnet@208.49.80.252 \
--to=wssddc@nospam.gis.net \
--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).