[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Building Emacs on MS Windows

From: Lars Hansen
Subject: Re: Building Emacs on MS Windows
Date: Fri, 07 Feb 2003 20:53:35 +0100
User-agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.2.1) Gecko/20021130

Jason Rumney wrote:

This is due to a shortcoming in CVS. We need DOS line ends on those
files when a release is made, which means they must be stored in
CVS with DOS line ends.  CVS does not have a concept of "leave the
line ends alone on this text file", it only understands "text" and
"binary".  On Windows, text files get an extra ^M blindly added
before every ^J by CVS, so if the lines already end in ^M^J, they end
up with ^M^M^J.  Making the files binary would fix this particular
problem, but then we would lose the ability to merge and diff with
previous versions.

The solution is to use a CVS client that does not change the
line-ends.  More recent versions of WinCVS have the concept
of a "Unix sandbox" to prevent line end conversion for a project.
Cygwin CVS also does not convert line ends by default.
Thank you for this information on CVS. It helped! When i use WinCVS and check the option "Checkout text files with the Unix LF" things work much better. Before I used TortoiseCVS, and I don't know if one can turn off LF conversions there.

I have not seen this before. It appears that an attempt to change
directory before running that command has failed.  If you are using a
non-default shell, try using cmd.exe instead.
I have looked a bit more into this. There is indeed some kind of change-directory problem. The problem shows up in Emacs 21.2 eshell under Windows. But there is no problem
with Emacs shell or Emacs eshell under GNU/Linux.
I will report this on address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]