From:	"John M. Aldrich" <fighteer AT cs DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: n
Date:	Wed, 26 Feb 1997 21:46:33 -0800
Organization:	Two pounds of chaos and a pinch of salt
Lines:	27
Message-ID:	<33151FB9.73F2@cs.com>
References:	<5f1s2a$bju AT oban DOT cc DOT ic DOT ac DOT uk> <5f2cet$cdp AT news DOT ox DOT ac DOT uk>
Reply-To:	fighteer AT cs DOT com
NNTP-Posting-Host:	ppp202.cs.com
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

George Foot wrote:
> 
> It's difficult to say without seeing the makefile itself, but check that
> the leading symbol on your command lines is a tab, not some spaces. Some
> editors (e.g. Win95's EDIT) have a non-disablable "feature" which replaces
> all the tabs in the file with an appropriate number of spaces... this
> makes these editors useless for writing makefiles.

Actually, Edit (for DOS 6.22 at least) can be convinced to use real tabs
instead of spaces, but this is probably a bug rather than a feature.  If
you load a file into Edit that contains raw tabs, it suddenly
"magically" stops converting them to spaces.  If this isn't the case in
the Win95 (aka DOS 7) version, then it was probably unintentional and
has been "fixed."

BTW, I don't want to start off another anti-MS flamewar, but is it
possible that MS deliberately disabled the Tab feature of Edit in order
to prevent people from writing makefiles for Unixy programs on DOS
boxes?  Or am I just being paranoid?

-- 
---------------------------------------------------------------------
| John M. Aldrich, aka Fighteer I  |        fighteer AT cs DOT com         |
| "Starting flamewars since 1993"  |   http://www.cs.com/fighteer   |
|  *** NOTICE ***  This .signature is generated randomly.           |
|                  If you don't like it, sue my computer.           |
---------------------------------------------------------------------

- Raw text -