[p4] please give me nocrlf back
Pavloff, Alex (IE) @ SONOMAEO
alex.pavloff at l-3com.com
Thu Jul 6 10:04:17 PDT 2006
I had this issue recently -- crossplatform development, with the target
silenty bombing out if it hit a CR in a shell script/config file.
Since I only have a few of these files, I just flipped the file type on
them to binary+D.
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Phlip
Sent: Wednesday, July 05, 2006 7:13 PM
To: perforce-user at perforce.com
Subject: [p4] please give me nocrlf back
I need to share a drive, edit files on it with one kind of editor, and
check the files in without Perforce screwing with their end-of-line
Unbelievably, the current system only allows me to pick _how_ Perforce
will screw with the end of line characters. Unix mode, Dos mode, Local
mode, etc. There is no feature to simply _not_ screw with them.
Put another way, all of my tools work correctly with various end-of-line
systems, except Notepad and Perforce.
I'm aware I can write check-in scripts that detect and adjust. Is there
a back-door to the old "nocrlf" command?
http://c2.com/cgi/wiki?ZeekLand <-- NOT a blog!!
perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user