Notepad++ v8.6.8 Release

Patryk

Hello,

FYI: Your repository hasn’t been updated.
/repository/8.x/8.6.8/
repository/8.x//8.6.8/npp.8.6.8.Installer.x64.exe

Coises

Is it intentional that the plugins list has not been updated since March 17th — 30 commits and 4 outstanding pull requests since then?

Plugin authors may be trying to implement the changes required for NPPN_GLOBALMODIFIED, but updated versions won’t get installed by most users if the list isn’t updated.

donho

@Coises

Is it intentional that the plugins list has not been updated since March 17th — 30 commits and 4 outstanding pull requests since then?

The release of March 17th is v1.7.1. The v1.7.2 has been released on May 2th, and it came with v8.6.6 - I forgot to announce the 1.7.2 release on Github. But you can check plugin list version in PluginAdmin (v1.7.2).

Last night while doing v8.6.8 release, I did git pull on the Plugin List repository, compiled it, and included it in v8.6.8. However, I forgot to increase the version to v1.7.3, so in PluginAdmin you will still see the version is v1.7.2, but I ensure you that pluginList is updated.

Sorry for the confusion.

LordEternal

@Patryk said in Notepad++ v8.6.8 Release:

Hello,

FYI: Your repository hasn’t been updated.
/repository/8.x/8.6.8/
repository/8.x//8.6.8/npp.8.6.8.Installer.x64.exe

I’m also seeing the same, empty folder at

http://download.notepad-plus-plus.org/repository/8.x/8.6.8/

Update: I see the files now. Thank you @donho!!

Coises

@donho said in Notepad++ v8.6.8 Release:

@Coises

Is it intentional that the plugins list has not been updated since March 17th — 30 commits and 4 outstanding pull requests since then?

The release of March 17th is v1.7.1. The v1.7.2 has been released on May 2th, and it came with v8.6.6 - I forgot to announce the 1.7.2 release on Github. But you can check plugin list version in PluginAdmin (v1.7.2).

Last night while doing v8.6.8 release, I did git pull on the Plugin List repository, compiled it, and included it in v8.6.8. However, I forgot to increase the version to v1.7.3, so in PluginAdmin you will still see the version is v1.7.2, but I ensure you that pluginList is updated.

Sorry for the confusion.

So the release listed as latest in the repository (1.7.1) is not actually what Notepad++ uses?

When I saw that listed as the latest release, I assumed that was why my plugin isn’t updated in the 8.6.8 plugins list, but I guess my pull request just missed the deadline by a couple days. :-(

donho

@Coises

So the release listed as latest in the repository (1.7.1 ) is not actually what Notepad++ uses?

No. v1.7.1 is outdated and not even included in v8.6.6.
With v8.6.8, the plugin list binary include the latest commit though its version was not increased to v1.7.3

When I saw that listed as the latest release, I assumed that was why my plugin isn’t updated in the 8.6.8 plugins list, but I guess my pull request just missed the deadline by a couple days. :-(

Could you check the version of your plugin in PluginAdmin of v8.6.8? I am pretty sure it’s updated if you have already committed your modification in the repository of PluginList.

Mark Olson

@donho said in Notepad++ v8.6.8 Release:

Could you check the version of your plugin in PluginAdmin?

I can’t speak for @Coises , but I have a version 8.6.6 portable build that lists JsonTools v7.2 as the most recent version of JsonTools, and that was the version that I added to the plugin list after v1.7.1 and before v1.7.2.

Coises

@donho said in Notepad++ v8.6.8 Release:

Could you check the version of your plugin in PluginAdmin of v8.6.8? I am pretty sure it’s updated if you have already committed your modification in the repository of PluginList.

I checked, I just misunderstood the problem. I made my pull request on June 2nd, and it looks like the cutoff must have been May 31st. Four pull requests are pending: mine, one for a new plugin, and two “dependabot” requests.

I know it’s probably too much to ask, but it would sure be nice for plugin authors if we got notice a couple days before the cutoff, so we could review whatever feedback, testing and reports we have at that time and decide whether our latest working version should replace what’s in the plugins list.

donho

@Coises

I checked, I just misunderstood the problem. I made my pull request on June 2nd, and it looks like the cutoff must have been May 31st. Four pull requests are pending: mine, one for a new plugin, and two “dependabot” requests.

Merged now. It will be in the next release for sure.

I know it’s probably too much to ask, but it would sure be nice for plugin authors if we got notice a couple days before the cutoff, so we could review whatever feedback, testing and reports we have at that time and decide whether our latest working version should replace what’s in the plugins list.

I guess that you’re talking about the same subject of the post:
https://community.notepad-plus-plus.org/topic/25565/notepad-rc-8-6-5-will-be-out-in-about-one-week

Yes. I will try to follow what we have agreed.
v8.6.8 is a special edition, so I didn’t follow the release procedure.

I take the chance to do my apology to the community for not respecting the release procedure - I will try to apply the procedure of 1. announcement before the RC, 2. RC & 3. release, even for the special edition.

Alan Kilborn

@donho said in Notepad++ v8.6.8 Release:

v8.6.8 is a special edition

Hmm… what makes an edition “special”?

Michael Vincent

@Alan-Kilborn said in Notepad++ v8.6.8 Release:

Hmm… what makes an edition “special”?

I’m assuming in this case it was the release message coupled with the release date. Though I don’t know if there is a set of dates, features, or other considerations that would justify a “special edition”.

I thought for a while there, there was always a January 1 Notepad++ release, though there wasn’t this past year (January 5 was closest with 8.6.1).

Cheers.

Jumo Mumo

I’m encountering an issue with the “Find In Files” feature in Notepad++. The “Hits” result, which previously displayed the number of matches found, has moved to the far right of the window.

I believe this might be a bug, as the previous location was far more convenient.

Could anyone confirm if this is an “improvement” update or a bug? If it’s not a bug, is there a way to move the “Hits” result back to its original position?

Thank you

Lycan Thrope

@Jumo-Mumo ,
I can confirm the issue, at least in the portable version. However, this seems to be in the progress dialog box which, at least on my old laptop, is hardly up long enough to be of consequence, IMHO…but it is confirmed.

xomx

@Jumo-Mumo
Yep, it is a v8.6.8 regression caused by the Add new dpi support to Find in Files Progress window commit.

donho

New feature or bug, it’s discuss-able.
But I see your point.
I’ll see what I can do about it.

donho

vs

Note that Hits is translatable so we have to reserve a max fix length.
As well for the number (not translatable but its length could be variable so the same max fix length is reserved).

Which version you prefer?

Lycan Thrope

@donho ,
The first one, with the count on the left, since that is what the prior version’s behavior was…I’d think it would be best to keep it consistent through versions if at all possible…but you are the architect, it’s your drawing/design. :-)

mkupper

@donho

While I also prefer Hits ### to be the left of the [Cancel] button can you nudge or float the button to the right should a translation of Hits ### be too long?

Do you support newlines in a translation? If so, don’t bother with nudging the button. Instead, it’s up to the translator to arrange the text so that it fits.

FabioTurati

@donho
Can you put it as is shown in @Jumo-Mumo 's screenshot, that is, above the progress bar, instead of below? This way the “Cancel” button doesn’t create problems if “Hits: #####” becomes too large. I think what Jumo wants is simply to have the number aligned to the left, and not to the right.

xomx

@Jumo-Mumo
Here is the fix to try: