unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Subject: [eric.pement@moody.edu: ediff merge fails on Win2K - RESOLVED!]
Date: Thu, 27 Mar 2003 14:04:55 -0500	[thread overview]
Message-ID: <E18ycgJ-00081g-00@fencepost.gnu.org> (raw)

Kifer thinks that call-process is the right place to fix this,
and that seems like a plausible idea.  Does anyone who works
on DOS or Windows want to fix this?


Date: Tue, 25 Mar 2003 11:11:59 -0600
From: Eric Pement <eric.pement@moody.edu>
To: bug-gnu-emacs@gnu.org
Subject: ediff merge fails on Win2K - RESOLVED!
Sender: bug-gnu-emacs-bounces+rms=gnu.org@gnu.org

This bug report will be sent to the Free Software Foundation [ ... ] 
Your bug report will be posted to the bug-gnu-emacs@gnu.org mailing list,
and to the gnu.emacs.bug news group.

  Several minutes ago, I sent in a bug report about ediff-merge-files
  failing on a Win2K machine using GNU Emacs 21.2.1. Specifically,
  Emacs complained that "diff3.exe" could not be executed, even though
  "diff3" was the proper version, was on the Windows PATH, and even
  though ediff-compare-files had worked successfully in the past.

  As I looked at the error message which I had to paste in with
  continuation lines because it would have been unreadably long, it
  occurred to me that perhaps this long line was the cause of the
  problem. In Windows 2000, the default environment setting for the
  TEMP variable is "%USERPROFILE%\Local Settings\Temp". Of course, the
  %USERPROFILE% is expanded to "C:\Documents and Settings\username",
  and three copies of this string (plus 3 different filenames) are
  appended to the diff3 command, thus creating a very long line.

  Here's how I resolved it:

  I manually created C:\TEMP (which is not in Windows 2K by default).
  I altered the TEMP variable to point to C:\TEMP. That's all I did;
  now everything works.

  My recommendation: I recommend that the ediff fuction calculate the
  length of the command line which will be sent to CMD.EXE, before the
  command is actually sent. If the length of the command line is
  greater than CMD.EXE allows, issue an error message suggesting that
  the user reduce the length of the TEMP environment variable. Thanks
  for listening.

--
Eric Pement - pemente[at]northpark.edu, eric.pement[at]moody.edu

             reply	other threads:[~2003-03-27 19:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-27 19:04 Richard Stallman [this message]
2003-03-27 20:10 ` [eric.pement@moody.edu: ediff merge fails on Win2K - RESOLVED!] Eli Zaretskii
2003-03-28 15:20   ` Richard Stallman
     [not found] ` <5.1.0.14.2.20030401083033.02fa8608@email.moody.edu>
2003-04-01 19:05   ` 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=E18ycgJ-00081g-00@fencepost.gnu.org \
    --to=rms@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).