Page 2 of 2 FirstFirst 12
Results 11 to 14 of 14
  1. #11
    Join Date
    Oct 2007
    Location
    Madison, WI
    Posts
    11,379

    Default

    Hello,

    We use the ¤ sign for Windows line endings, which should appear on a side that is hosted on a Windows machine. If both sides are Linux, the expected sign is ¶ for the Linux line endings. Older Mac line endings use the << character, although many modern OSX editors use Unix ¶ line endings.

    If both sides are SFTP locations on Linux servers, and you are running BC4's Linux client, ¶ display makes sense (as well as the text "Unix" in the top status bar of each pane). Is there a method you are using that gives the files the Windows line ending? Or are you trying to inject the Windows line ending (Edit menu -> Convert -> Line endings)?
    Aaron P Scooter Software

  2. #12
    Join Date
    Apr 2008
    Posts
    70

    Default

    Tested as follows :

    With profile as "Auto"

    * Started session. Session is two folders on the same (Ubuntu) server, via SFTP.
    * Content is PHP source code with Unix (LF) file endings
    * On compare, both sides displayed as UNIX / Pilcrow correctly
    * Left side is a Git clone
    * Added/removed space to left file to set dirty flag. Saved file.
    * Git now identifies file as changed
    * Vim now shows file has DOS file endings
    * Reloading compare INCORRECTLY identifies left file as UNIX
    * Running dos2unix on file restores it to unchanged condition
    * "Auto" saves file with PC endings regardless of detected / presented endings

    With profile as "Binary"

    * Reload compare
    * Correctly identifies file as PC endings
    * Also correctly identifies file after being fixed back to LF endings
    * Saves file with presented endings

    Have attached log with all options on and repeated examples of these steps.
    Attached Files Attached Files

  3. #13
    Join Date
    Oct 2007
    Location
    Madison, WI
    Posts
    11,379

    Default

    Thanks for these steps. I had been using BC4 to verify the line ending characters, and using an external tool or BC4 in Binary Mode helps reveal an issue. We'll investigate to figure out what's going on here.
    Aaron P Scooter Software

  4. #14
    Join Date
    Oct 2007
    Location
    Madison, WI
    Posts
    4,584

    Default

    The SFTP ASCII transfer bug is fixed in Beyond Compare 4.1.3.
    Chris K Scooter Software

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •