Sender: rich AT phekda DOT freeserve DOT co DOT uk Message-ID: <3CF0ACBE.A77834E7@phekda.freeserve.co.uk> Date: Sun, 26 May 2002 10:37:02 +0100 From: Richard Dawe X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.19 i586) X-Accept-Language: de,fr MIME-Version: 1.0 To: djgpp-workers AT delorie DOT com Subject: Re: emacs under w2k References: <10205192036 DOT AA17719 AT clio DOT rice DOT edu> <74330986783 DOT 20020520124839 AT softhome DOT net> <3CEF6292 DOT 41C13BEC AT phekda DOT freeserve DOT co DOT uk> <2110-Sat25May2002140607+0300-eliz AT is DOT elta DOT co DOT il> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: djgpp-workers AT delorie DOT com Hello. Eli Zaretskii wrote: > > > Date: Sat, 25 May 2002 11:08:18 +0100 > > From: Richard Dawe > > > > Eli, BTW config.bat in Emacs CVS does 'cd lispintro' at one point. This > > does not work if you've extracted the sources using SFN. > > Ugh. Does cmd.exe on NT support the usual trick to detect a > non-existing directory? That is, will the following solve the > problem? > > if exist lispintro\nul cd lispintro > if exist lispintr\nul cd lispintr Yes, just tried it and it works. Rather than checking for nul, why not check for a file that you know exists in lispintro (aka lispintr), say makefile or readme? > I seem to recall that some recent Windows version (W2K? XP?) doesn't > like this method, though. Hmm. Yes, I don't think it works reliably. See Andrew Cottrell's mail entitled "Re: Make 3.791 on Windows 2000 test" and dated Tue, 24 Jul 2001 22:28:43 +1000. I believe Microsoft made changes to the support of the \ feature, because people were using it to exploit path-parsing problems in Microsoft IIS on earlier versions of NT. Bye, Rich =] -- Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]