----- Original Message -----
From: "Paul G." <pgarceau@...>
Sent: Saturday, May 11, 2002 3:27 PM
Subject: Re: [Mingw-msys] postinstall on Windows 9x
> As to the out of environment space problem. We discussed a couple of
workarounds for this earlier. You might want
> to review the archive of the mailing list to see what those were.
Yes, I know about modifying shortcuts and setting COMSPEC to launch
command.com with /e.
> (still smarting from my fauxpas committed earlier this week)
I understand that you need to give the obvious answers sometimes because new
users overlook them. I also understand that Earnie does not like other users
to be misinformed by some of your answers :).
> As to cvs clients. I am using Wincvs. V1.2 (last stable) has an option
to use unix line ending instead of
> converting things to \r\n stuff (are those slashes correct?).
I have used WinCVS before, but I am using the "official" command line CVS
from cvshome.org (and TortoiseCVS, which calls the command line version). It
would be nice to have a solution that works with this client.
> Also, when unzipping or dearchiving the stuff from the project files page,
you can set your winzip client to not
> be "smart" about converting line ending. Not sure why I mentioned that
little bit, just felt appropriate.
I know, source code from tar.gz files is fine. But in future if I help with
development of MSYS I would need to use CVS.
> On 11 May 2002 at 14:12, Luke Dunstan wrote:
> > Hi,
> > Apparently Windows 98 cannot handle batch files with Unix line endings,
> > pi.bat does not work (it treats the three lines as one PATH command).
> hmm..I thought pi was a .sh script.
pi.bat is a batch file that launches pi.sh:
It would be better to modify pi.sh or the Inno Setup configuration so that
the batch file is no longer required. I'm not sure why the PATH needs to be
set here, since /etc/profile does.
> > However, with DOS line endings I still get an "Out of environment space"
> > error, so perhaps the batch file needs to be launched differently (I
> > checked what Inno Setup allows yet). Also, msys.bat works because most
> > have CRLF, but a few of the comment lines have only LF, which is of
> > ignored by Win9x. The only problem with msys.bat is that editors like
> > Windows vim open it as a Unix text file because SOME lines have no CR,
> > just looks ugly with ^M all over the place.
> A good source code editor, also free, is VIDE. One of the VIDE editor
options allows you to clean up your
> source code and/resave it with unix line endings or with Win32 line
endings if you ever need to clean up a unix
> formatted source code.
Vim has no problem handling DOS or Unix line endings, and can easily convert
between them. It just defines a DOS text file strictly as having \r\n on
every line, though I can easily remove \r with a regex substitution. But the
real issue is that all lines should have \r\n in batch files because Win9x
requires it. It is just by chance that the lines that have no \r are
comments, and are followed by a comment.
> Paul G.