🚀 go-pugleaf

On Monday, in article <816330614snx@holly.demon.co.uk>
     mcr@holly.demon.co.uk "Mark Rogers" wrote:

MR> In article <815959624snz@wash.demon.co.uk>
MR>    John Washington <john@wash.demon.co.uk> writes:
MR> > 
MR> > You could store your script file somewhere else, and generate
MR> > autoexec.net from it with a pre-processor.  And that's actually
MR> > what I do myself, though not to make comments prettier.
MR> 
MR> It makes maintainance more difficult - or, at least, more time consuming.

If you'd said more inelegant I'd have agreed.

Make a file x.bat (I suppose a Win95 user might call it
modify_my_autoexec_net.bat) something like:

        edit autoex.bat
        prepro <autoex.bat >autoexec.bat

MR> I guess you could convert demon.bat into a make file, forcing 
MR> autoexec.net to be rebuilt if it has changed before net.exe is run, but I 
MR> like a simple life :-)

Or keep demon.bat pretty much as is, just adding one line
to call 'make'.  However, I'd rather not have that overhead
every time I call Demon, since the other way is adequate.

MR> (Actually, the idea of converting demon.bat into a make file sounds like 
MR> the sort of thing I'd do on a wet Sunday; sad, isn't it?)

I'd join you creating alt.wet-sunday.things-to-do, except
I've just discovered dry rot in my bathroom, so I know
what I'll be doing for the next few Sundays.  :-(

[rest of post censored for being even more off-topic]

--
John Washington