Notepad++ 7.6.5 Release Candidate

  • Please check Notepad++ 7.6.5 Release Candidate here:

    If everything is fine then the official release will be available in a couple of day.

    Thank you.

  • thank you very much @donho.
    the list of fixes and enhancements is huge 👍💚❤️.

    i only found two small things, which could be quickly improved before release, if you like any of them:

    • all portable versions (except minimalist) contain an old config.xml from 2018.12.25.
      this overrides newer default settings, like Use new style dialog.
      config.xml could be removed completely from the zip/7z releases, as it will be created on startup, using the new defaults.

    • a possibly user relevant entry is missing at the change.log:
      15. Fix UDL language marker bullet position, if UDL Name exceeds 14 characters, extend UDL names to max 64 characters.

    now to the good stuff:

    • autodetect character encoding:
      autodetection is working great again.
      i’ve re-tested a few of the open issues at the tracker with success and posted the ones verified to be closed at your commit, in case you like to empty the tracker a bit.
      (i did that as a little compensation for being so insisting 😉)

    • new file status auto-detection enhancement:
      your gui change for the new file status autodetection is perfect and intuitive.
      (it would have driven me crazy as well, to have to deselect one option, before i can select the other option)
      reader’s note: this enhancement function is for all users, that usually have a ton of opened file tabs. it enables to only check the foreground tab for external file modification, avoiding multiple file change dialogues when changing focus to another application and back to notepad++.

    • open in browser enhancement:
      the new, temper safe, view current file in browser, including edge, is very nice:

    • udl names fix and enhancement:
      longer udl names, including Markdown (Default) are now shown correctly as selected.

    • undo enhancement:
      it is now possible to undo changes, even after a user reloads a file manually, or if it get’s changed from the outside.

    and much, much more good stuff.

    ps @SinghRajenM : once more 👍❤️ + community group hug and a beer 😉

  • @Meta-Chuh said:

    the list of fixes and enhancements is huge

    What am I missing? Where is this “list”?

  • I asked you to separate the run command files and macros …and this is not)

  • @Alan-Kilborn said:

    What am I missing? Where is this “list”?

    If you grab one of the zips from Don’s link (or presumably the installer) and dig into the change.log that’s included, you can find said “list”.

  • @Alan-Kilborn

    What am I missing? Where is this “list”?

    In aure)

  • @PeterJones said:

    If you grab one of the zips

    Ah, okay…I’m used to software where you can quickly view the changes BEFORE bothering to grab it (if you don’t want it based on said list contents!)


  • @andrecool-68 said:

    I asked you to separate the run command files and macros

    We have to be glad for what we DID get, and not make glib remarks about what we didn’t. :)

    Unless you go to the Boycott / F*ck Notepad++ area. :)

  • @Alan-Kilborn said:

    view the changes BEFORE bothering to grab it

    Well, yes. But this is a release candidate, not a final release.

    I’m actually quite happy that Don took the RC route; hopefully, that will mean the experienced users will be able to help find problems before the general public starts asking us all sorts of repeated questions here. :-)

  • @Alan-Kilborn
    I don’t need falsification …I need a solution)

  • @andrecool-68

    “falsification” ?

    And perhaps it is time for the eternal refresher: Notepad++ is free software.

  • @Alan-KilbornI
    have no desire to include insult here …I asked the author to make changes …and if I’m not mistaken you are not the author of the program)

  • to all:

    guys, please don’t over-post this topic !!!

    let’s only focus on thorough testing, reporting eventual bugs, or showing new features.
    otherwise this release candidate attempt will fail.

    btw: i expect that everyone who just posted here, has already downloaded, installed and tested the 7.6.5 release candidate.

  • @Meta-Chuh said:

    guys, please don’t over-post this topic

    Good point, sorry.

    I noticed that the RC refers to itself as “7.6.5”. In the about box. This is kinda bad as if it isn’t the final release then what does one do when reporting/evaluating-reported bugs? Always have to pay attention/ask-for version AND build time ?? We don’t want to be chasing down bugs because someone is accidentally using a RC (later down the line) and keeps insisting something isn’t working in 7.6.5 (when it is working in the real 7.6.5, just not the RC). Does this make sense to people??

    Or if 7.6.5 RC fails, does that mean there is no real 7.6.5 release and we go to 7.6.6 RC, etc.?

    Just wanna understand what the RC scheme plan is, if there is one…

  • @Alan-Kilborn
    There’s no special scheme plan.
    If RC is good, then the same binaries will be published as official release. Otherwise the regression is fixed then the same version number with RC2, etc…
    The RC is not supposed to be out of community, so I think it’s OK. In the worst case, we have the build time to compare with.

Log in to reply