Please separately specify if any changes have been made in plugin arrangement in this version after recent so many changes?

no user relevant changes to the plugins arrangement have been made, so if you are on 7.6.3, and you update to 7.6.4, you will not experience any changes regarding your existing plugins.

one thing you are going to like: 7.6.4 has the built in feature to open your specific plugins folder directly in an explorer window.
so you will not have to remember any past or present plugins locations, regardless where and how notepad++ is installed.
(this feature applies to both installed and portable versions, both 32 and 64 bit)

ps: if any supportive relevant changes are made or omitted, they will be posted as additional supportive notes, shortly after a release.

Seems you have still not started beta release concept?

the “beta” testing, using e.g. the appveyor artifacts, is still available and has been available for a long time.
i have given you a basic, but maybe too extensively technical guide, on how to test any version before it’s public release, a few weeks/months ago.

as the guide was, retrospectively seen, too technical, i (we) will try to write a simpler guide, suitable for the general public, as soon as i (we) can find the time to do so.

Seems you have still not started beta release concept?

Thanks.

Auto-updater won’t be triggered for this release.

v7.6.5 is coming.

ps: if you need information about the update triggering not working for 7.6.1 to 7.6.3 in the mean time while waiting:

the updater web server requires the notepad++ updater to send its version with a single period only, like 7.62 for version 7.6.2.

unfortunately versions 7.6.1 to 7.6.3 will send the string 7.6.1 to 7.6.3 to the updater url, which would not be recognised by the update server and causes a repeated loop of triggering “a new update is available” even though you were on the latest version.

please respect this decision to suspend all updates, as it would have caused major problems to millions of users, which would have been impossible to cope at any project or community level.

i apologise again, that you are not able to respond to follow up posts without having to wait for another 20 minutes.

this restriction for your account will be removed as soon as you have either a sufficient amount of undeleted posts, or you have reached the threshold limit of upvotes.

I understand the 7.6.0 update is frozen, but are updates from 7.6.x to 7.6.y also frozen? I’m on 7.6.3 and don’t see the update to 7.6.4.

yes, due to technical reasons it is currently not possible to update 7.6.3 to 7.6.4 as it will affect other versions which would produce a major supportive issue.

currently it is not possible to separate updates to be deployed and update specific versions to newer specific versions.

New question: Is there any reason 7.6.x aren’t set to auto update to the latest 7.6.y? And why does the post say otherwise?

yes, it is currently not possible to separate updates to be deployed, and all versions would get the same update, which is currently a concern.

i apologise for the project’s sentence “Auto-updater will be triggered in few days if there’s no critical issue found.” but it clearly states the words if there's no critical issue found and the developers as well as the community has found issues.

i hope this information might be of help to you.

New question: Is there any reason 7.6.x aren’t set to auto update to the latest 7.6.y? And why does the post say otherwise?

It’s really the same question – or, rather, the same answer. Don’s “in a few days” has historically been more than a week, and usually at least 2 weeks. It’s only been a week since the announcement, so I wouldn’t expect the auto-update to trigger for another week or so.

New question: Is there any reason 7.6.x aren’t set to auto update to the latest 7.6.y? And why does the post say otherwise?

Auto-updater will be triggered in few days if there’s no critical issue found.

I understand the 7.6.0 update is frozen, but are updates from 7.6.x to 7.6.y also frozen? I’m on 7.6.3 and don’t see the update to 7.6.4.

this is a normal behaviour on machines with enabled uac and has been like that before 7.6.2.

if you have uac enabled at your windows settings, you have to run notepad++ as administrator in order to add your desired extensions to the windows explorer, as notepad++ would otherwise not have the permissions to set them.

please close notepad++, right click on the notepad++ icon and select run as administrator (exécuter en tant qu'administrateur).

then add all your desired extensions to the administrative account.
restart notepad++ normally and check all your added extensions.
note: you might have to add some of them at the user level too, but once they are set for the administrator account, you will have the permission to save them to your current windows user account explorer settings.

we already have the two commands Remove Empty Lines and Remove Empty Lines (Containing Blank characters), which deletes all the empty lines, on the entire document. Could it be possible to…act on current normal selection, only, if such a selection exists?

@donho said:

these enhancements have to wait for sure

If anybody wants this functionality TODAY, it is just an edit of shortcuts.xml away; add following into macros section, restart N++, look in Macros menu:

    <Macro name="Remove Empty Lines From Selection" Ctrl="no" Alt="no" Shift="no" Key="0">
        <Action type="3" message="1700" wParam="0" lParam="0" sParam="" />
        <Action type="3" message="1601" wParam="0" lParam="0" sParam="^\R" />
        <Action type="3" message="1625" wParam="0" lParam="2" sParam="" />
        <Action type="3" message="1602" wParam="0" lParam="0" sParam="" />
        <Action type="3" message="1702" wParam="0" lParam="640" sParam="" />
        <Action type="3" message="1701" wParam="0" lParam="1609" sParam="" />
    </Macro>
    <Macro name="Remove Empty And Lines With Blanks From Sel." Ctrl="no" Alt="no" Shift="no" Key="0">
        <Action type="3" message="1700" wParam="0" lParam="0" sParam="" />
        <Action type="3" message="1601" wParam="0" lParam="0" sParam="^\h*\R" />
        <Action type="3" message="1625" wParam="0" lParam="2" sParam="" />
        <Action type="3" message="1602" wParam="0" lParam="0" sParam="" />
        <Action type="3" message="1702" wParam="0" lParam="640" sParam="" />
        <Action type="3" message="1701" wParam="0" lParam="1609" sParam="" />
    </Macro>

P.S. I know that guy038 knows how to do this and is requesting native functionality for these commands, so no need to point that out to me like I don’t realize it. :)

@berezovskyi

FYI, the discussion on HN suggests an OSS signing cert for €25.

The price is not really an issue, the CN as Notepad++ is.

@guy038 said:

As for the sort operations, would it be possible that this command only acts on a normal selection of text ? So, empty lines, in other parts of current document, would not be deleted ;-))

Now, Don, we already have the two commands Remove Empty Lines and Remove Empty Lines (Containing Blank characters), which deletes all the empty lines, on the entire document. Could it be possible to harmonize these commands ? This means that they would act on current normal selection, only, if such a selection exists.

I will consider it. However, I have so many priorities at this moment, these enhancements have to wait for sure.

To which I say: @donho himself is definitely the quarterback!

he’s the OWNER of the team, so if he likes, he can sit down, relax and watch the game with a bucket of popcorn 😉

…to personally support you as quarterbacks, linemen, and defense

To which I say: @donho himself is definitely the quarterback!

@guy038 said:

Renaming new # tabs should be a very useful feature, for people which keeps plenty of these no-saved tabs

And I’m sure this new feature will bring out more data loss stories, if the problems related to that are still not fixed.

Could it be possible to harmonize these commands ?

Amen. Soooo confusing the way it currently is.

please don’t forget to take a break once in a while again @donho .

i have probably read all of your recent publications and code changes, noticed the increased amount of time you spent lately, with all the recent worries and additional requests, and i admire how you endure all of it.

some words in the hope it might relieve a fraction of any possible stress: we have a lot of workarounds and answers for almost everything that is not fixed or implemented yet, and we will give our best to find more, to personally support you as quarterbacks, linemen, and defense.

with sincere and very grateful regards, MetaChuh

Many thanks for this new 7.6.4 version ! I’m thinking about :

• Renaming new # tabs should be a very useful feature, for people which keeps plenty of these no-saved tabs

• The enhanced UDL system, more flexible

• The practical mouse gesture Shift + Mouse Wheel, for horizontal scrolling

• The new line operation Remove Consecutive Duplicate Lines

By the way, did anyone notice that the Remove Consecutive Duplicate Lines , implicitly, give us a new command, which could be named Deletes Excess Empty / Blank lines ? Indeed, it just keeps one empty line, from a block of several empty lines and one blank line, from a block of several identical blank lines !

However, this implicit behavior, when using the Remove Consecutive Duplicate Lines option, may not be desired ! So, may I ask you, Don, for an improvement : As for the sort operations, would it be possible that this command only acts on a normal selection of text ? So, empty lines, in other parts of current document, would not be deleted ;-))

Now, Don, we already have the two commands Remove Empty Lines and Remove Empty Lines (Containing Blank characters), which deletes all the empty lines, on the entire document. Could it be possible to harmonize these commands ? This means that they would act on current normal selection, only, if such a selection exists.

Best regards,

guy038

The link to the cert issuer is https:// en.sklep.certum .pl/ data-safety/code-signing-certificates/open-source-code-signing-984.html (please fix your Akismet settings).

can you please go to settings > preferences > default directory and have a look at your use new style dialog setting, as seen at the screenshot below.

then enable it if it is not set, or disable it if it is set already, and retry.
does changing this setting make any difference in any behaviour for you ?

if it does not change, try to create a new local user account, log into it and retry saving anything to this new account’s desktop using notepad++.
if this works, you will have to check your original account’s permissions and hive.

for that i would suggest you to open a new topic separately at either the category help wanted, or general discussion, to keep it separate from 7.6.4 release topics, as this would not be related.

best regards

-open new tab
-write random text
-try to save or save as
-write name test.txt
-select Desktop as folder to save file
-click save button
-error appears:

File not found.
Check the file name and try again.

Notepad++ v7.6.4 (64-bit)
Build time : Mar 6 2019 - 02:58:24
Path : C:\Program Files\Notepad++\notepad++.exe
Admin mode : OFF
Local Conf mode : OFF
OS : Windows 10 (64-bit)
Plugins : mimeTools.dll NppConverter.dll

even in Admin mode:

Notepad++ v7.6.4 (64-bit)
Build time : Mar 6 2019 - 02:58:24
Path : C:\Program Files\Notepad++\notepad++.exe
Admin mode : ON
Local Conf mode : OFF
OS : Windows 10 (64-bit)
Plugins : mimeTools.dll NppConverter.dll

Thanks for your help

here are some further 7.6.4 testing results if you need them.
(7.6.4 commits only, nothing of weight found 👍)

Use new style open/save file dialog by default:

issue: all four portable versions, both zip and 7z, both x64 and x86, contain an old config.xml, dated to 2018.12.25 18:16, which still has Use new style file dialog disabled.

• predicted issue weight: 0-1
• possible fix: remove the physical config.xml file from all portable zip and 7z packages.
  it will be created correctly on first notepad++ startup, if it is not present yet (Parameters.cpp/Parameters.h).

success: all 7.6.4 minimalist 7z packages (x86/x64) work as expected, as they do not contain config.xml as a physical file.
notepad++ will correctly create one on first run&exit.

success: all installers (x86/x64) work as expected, as they do not contain a config.xml as a file resource.
notepad++ will correctly create one on first run&exit, inside of %AppData%\Notepad++\ of the current user.

Fix Markdown not working in installer package of v7.6.3:

success: the 7.6.4 installers (x86/x64) will correctly deploy userDefinedLang-markdown.default.modern.xml to %AppData%\Notepad++\userDefineLangs of the user account, which is used to install notepad++ (but only this account).

issue: if more than one user account exists on a machine, markdown will not be deployed to any user accounts, except the user account that was used to install notepad++ 7.6.4.

• possible fix: deploy userDefinedLang-markdown.default.modern.xml via Parameters.cpp to %AppData%\Notepad++\userDefineLangs if it does not exist.
• predicted issue weight: 1-4
  see the pre-release testing report for details.

ps: again many thanks for everything that has been implemented and not been mentioned yet … not mentioned, because it works flawlessly so far 👍

It appears the windows installers for 32 and 64bit are no longer digitally signed

Yes, that was intentional. It was mentioned on the https://notepad-plus-plus.org/news/notepad-7.6.4-released.html page, as well as in the change log that @meta-chuh quoted here.