Community
    • Login

    Bug with the "CRLF" end of line

    Scheduled Pinned Locked Moved Help wanted · · · – – – · · ·
    12 Posts 4 Posters 146 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • guy038G
      guy038
      last edited by guy038

      Hello, @m-andre-z-eckenrode and All,

      Well, my present releases 8.8.1 and 8.8.0 are, in fact, the versions 8.8.1_RC2 and 8.8.0_RC2, without any EXTRA plugin

      Thus, I decided to download, successively, the npp.8.8.1.portable.x64.7z, npp.8.8.portable.x64.7z and npp.8.7.9.portable.x64.7z archives and repeat the test !

      So :

      • I extracted the contents of the npp.8.8.1.portable.x64.7z archive in a test folder :

      • I launched Notepad++ v8.8.1

      • In Preferences... :

        • I disabled the Enable session snapshot and periodic backup, in the Backup section

        • I checked the custom color for EOL in the Editing 2 section

      • Then, I loaded my post about the CRLF bug

      => I was able to reproduce what I explained in my previous post :

      4bb56492-80e1-4917-8af7-81b42ba0e84c-image.png

      • Then I deleted all the files of this test folder

      • I extracted the contents of the npp.8.8.portable.x64.7z archive in the test folder

      • I re-ran the same process as above

      => Again, I was able to get the same behavior that the one described in my previous post :-((

      • I deleted all the files of that test folder

      • Finally, I extracted the contents of the npp.8.7.9.portable.x64.7z archive in the test folder

      • I re-ran the same process as before

      => This time, everything was OK. Indeed, NO way to get the LF character at end of a line and the CR character at start of the next line, with the v8.7.9 release !

      Best Regards,

      guy038

      M Andre Z EckenrodeM 1 Reply Last reply Reply Quote 0
      • M Andre Z EckenrodeM
        M Andre Z Eckenrode @guy038
        last edited by

        @guy038 said in Bug with the "CRLF" end of line:

        Indeed, NO way to get the LF character at end of a line and the CR character at start of the next line, with the v8.7.9 release !

        Clarification, please: You actually mean CR at the end of one line and LF at the end of next, don’t you?

        1 Reply Last reply Reply Quote 1
        • guy038G
          guy038
          last edited by guy038

          Hello, @m-andre-z-eckenrode and All,

          Yes, my bad ! Of course, I meant :

          NO way to get the CR character at end of a line and the LF character at start of the next line

          BTW, @m-andre-z-eckenrode, are you able to reproduce ?

          BR

          guy038

          M Andre Z EckenrodeM 1 Reply Last reply Reply Quote 0
          • PeterJonesP
            PeterJones @guy038
            last edited by PeterJones

            @guy038,

            Can you reproduce this weird bug ?

            I can. in v8.8.1 (update: fresh unzip of portable, no extra plugins, etc) , if I follow your instructions (and resize the window-width and/or zoom), I can get it to wrap between the CR and LF, and when I do, down-arrow from above gets “stuck” between CR and LF (though other arrows and page keys allow me to keep navigating to either side of the row of hyphens. I also checked in v8.7.9, and confirmed it will not let me change the width and/or zoom in such a way that it wraps between – it is always either both on the original line, or the final hyphen and the CRLF on the wrapped line, never in between.

            I can confirm, and would recommend creating an Issue about it.

            1 Reply Last reply Reply Quote 1
            • M Andre Z EckenrodeM
              M Andre Z Eckenrode @guy038
              last edited by

              @guy038 said in Bug with the "CRLF" end of line:

              are you able to reproduce ?

              As stated above, I could not reproduce what you describe in my fully-plugin-loaded installation of v8.8.0 (which is the 32-bit version, in case that matters). I have not tried with any portable/x64/plugin-disabled version. I’ll probably end up installing v8.8.1 32-bit later today (after completing the latest round of Windows updates), and will try to make a point of seeing if there’s any difference in behavior with it.

              1 Reply Last reply Reply Quote 0
              • guy038G
                guy038
                last edited by

                Hi, @m-andre-z-eckenrode, @peterjones and All,

                I’ve just downloaded the v8.8 - 32 bits release and I do verify the bug, either !?

                Get stuck on line 24 when going downwards !

                264bf895-1a18-4800-bef9-6d22fc522ad2-image.png

                Best Regards,

                guy038

                M Andre Z EckenrodeM 1 Reply Last reply Reply Quote 0
                • M Andre Z EckenrodeM
                  M Andre Z Eckenrode @guy038
                  last edited by

                  @guy038

                  Based on what I observed in your screenshot, I opened a new NPP window, maximized it and changed my settings to UTF-8 and the Courier New font (I normally utilize a half-screen window size, ANSI text and the Georgia font), and retested your prescribed steps, and can now confirm the bug you describe under those conditions. Upon doing some basic process of elimination — encoding restored to my normal default of ANSI, but font and window state kept as same as what you appear to have used — your bug did NOT materialize, so I’d say that encoding is a factor.

                  1 Reply Last reply Reply Quote 2
                  • xomxX
                    xomx @guy038
                    last edited by

                    @guy038 said in Bug with the "CRLF" end of line:

                    Can you reproduce this weird bug ?

                    I also can.

                    Seems to be a consequence of updating the Scintilla to v 5.5.6, relevant commit:
                    https://github.com/notepad-plus-plus/notepad-plus-plus/commit/5c1813185aa111d6247de39e3d7049ebef0960e0

                    xomxX 1 Reply Last reply Reply Quote 3
                    • guy038G
                      guy038
                      last edited by

                      Hi, @m-andre-z-eckenrode, @peterjones and All,

                      Ah… bravo, @m-andre-z-eckenrode ! You’ve found out the root of the problem. It’s indeed an encoding dependent bug !

                      I verified that all the options, below, produce that bug :

                      • UTF-8

                      • UTF-8-BOM

                      • UTF-16 BE BOM

                      • UTF-16 LE BOM

                      • Character Sets

                      • Convert to UTF-8

                      • Convert to UTF-8-BOM

                      • Convert to UTF-16 BE BOM

                      • Convert to UTF-16 LE BOM

                      The two options, which work correctly and do NOT produce that bug, are :

                      • ANSI

                      • Convert to ANSI

                      BTW, I generally used UTF-8 files, with the Consolas font. So this bug does NOT seem to be font dependent !

                      So, I will create an issue, regarding this bug, very soon !

                      Cheers,

                      guy038

                      1 Reply Last reply Reply Quote 2
                      • xomxX
                        xomx @xomx
                        last edited by

                        STR video:
                        https://github.com/notepad-plus-plus/notepad-plus-plus/pull/16373#issuecomment-2883743117

                        1 Reply Last reply Reply Quote 4
                        • First post
                          Last post
                        The Community of users of the Notepad++ text editor.
                        Powered by NodeBB | Contributors