Page 1 of 1

Perforce Line Endings

Posted: Wed 17 Feb 2016 17:56
by Bluebeary7
We have our Perforce workspaces set up to use Unix line endings (LF). Our machines are running Windows 10 with VS 2015.

Whenever we do a compare using any tool (Code Compare, VS Internal, or Araxis), we sometimes get double spaced lines and files converted to Windows (CRLF). When we do a Get from Perforce, the files come in as LF as they're supposed to. RA seems like it's converting to Windows (or OS specific). Not all files get converted to double spaced.

Any idea what's going on and how to fix it?

Thanks,
Rob

Re: Perforce Line Endings

Posted: Thu 18 Feb 2016 12:00
by Artem
Review Assistant keeps line endings as is. It just calls Perforce to get file from depot:

Code: Select all

p4.exe -p TCP:YOUR_SERVER:1666 print -o C:\PATH_TO_OUTPUT_FILE //DEPOT/YOURP_ROJECT/YOUR_FILE@REVISION_NO
Maybe, you should use the share option in your workspaces:
https://www.perforce.com/perforce/doc.c ... lient.html

Also, take a look at the following article: http://answers.perforce.com/articles/KB/3096

Re: Perforce Line Endings

Posted: Fri 19 Feb 2016 02:11
by Bluebeary7
Thank you. I will try that Share option.