Author Topic: Perforce and CRLF vs LF  (Read 1421 times)

jporkkahtc

  • Senior Community Member
  • Posts: 1837
  • Hero Points: 178
  • Text
Perforce and CRLF vs LF
« on: September 16, 2014, 09:37:08 pm »

Whenever I attempt a DIFF operation with source control (Perforce), slick gives this dialog:
"These files have differen end of line characters"
With 4 action buttons.


#1: Slick shouldn't complain, because there is no difference in line endings. The problem is the way that slick calls "p4 print", the temporary file that it gets from Perforce ends up with a single CRLF as the last thing in the file. [size=78%](I'm running on Windows, and my Perforce client is set to "LineEnd: UNIX" so that all files have LF only line endings).[/size]


#2: Can this dialog get a checkbox: "[] Don't ask me this again" ?




Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2373
  • Hero Points: 132
Re: Perforce and CRLF vs LF
« Reply #1 on: September 17, 2014, 02:44:35 pm »
I set my client to UNIX line endings and so far I still cannot reproduce it.  I would really like to reproduce this so I can fix the underlying issue rather than just a put a checkbox on the dialog.

I'm able to reproduce this now, let me see what I can do about it.
« Last Edit: September 17, 2014, 03:38:09 pm by Dan »

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2373
  • Hero Points: 132
Re: Perforce and CRLF vs LF
« Reply #2 on: September 17, 2014, 06:51:07 pm »
In the next beta drop we will match the new line characters of the local file, so you will not see this prompt anymore.