delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2012/07/07/02:54:41

X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
Date: Sat, 07 Jul 2012 09:54:05 +0300
From: Eli Zaretskii <eliz AT gnu DOT org>
Subject: Re: Ispell
In-reply-to: <MPG.2a61256b7098af43989680@news60.forteinc.com>
X-012-Sender: halo1 AT inter DOT net DOT il
To: djgpp AT delorie DOT com
Message-id: <83sjd412pe.fsf@gnu.org>
References: <MPG DOT 2a61256b7098af43989680 AT news60 DOT forteinc DOT com>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

> From: "Stephen W. Bullington" <swb AT key-net DOT net>
> Date: Fri, 6 Jul 2012 18:00:36 -0400
> 
> I can't get ispell to work with DJGPP Emacs 23.3 on pure DOS.  I have 
> Emacs installed on two 8.3 file-name machines, 1) a DOS 6.22 one and 2) 
> an OS/2 Warp 3 (blue spine) one.  Ispell doesn't work on either, using 
> Emacs (in both cases it works OK from the command line, though).  When I 
> try to use it I get the message "Failed to open temporary file:  no such 
> file or directory (ENOENT), detmp.XXX".  I get the same message if I try 
> to run a shell command.  I also have DJGPP Emacs installed on a Windows 
> 98SE box, with LFN=Y, and Ispell works fine there.
> 
> What am I doing wrong under pure DOS?

Not sure what is going on.  One potential problem could be that you
don't have any of the following environment variables defined: TMPDIR,
TMP, TEMP.  If none of these are defined, Emacs will try to open the
temporary file in C:/temp, and if you don't have that, either, it will
fail.  It will also fail if one of the above environment variables is
set, but points to a non-existent directory.

djgpp.env, the file all DJGPP programs read to set up their
environment, defines TMPDIR to point to the 'tmp' subdirectory of the
directory where you have djgpp.env.  Could it be that this directory
doesn't exist on those machines where you see the problem?

If none of the above helps, I'm clueless.  If you can build Emacs
yourself and you can debug the resulting binary with GDB, perhaps you
could step through the code (I can tell you where exactly) and report
what you see.  I myself don't have access to a plain DOS machine for a
long time now, and can only run the DJGPP build of Emacs on Windows.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019