Notepad++ v8.3 release

[Clem Patafio]

I have 2 PCs, an HP Envy desktop and a Dell Inspiron laptop. Both are running Windows 10 Home 21H2.

I’ve updated both to Notepad++ v 8.3 and both have the same plugins installed. However, whenever I start or shutdown NPP on the HP, I get an error that I have to click through to open or close NPP. The error states “An exception occurred due to plugin: nppAutoDetectIndent.dll” and the next line says “Exception reason: Access violation”

If I uninstall nppAutoDetectIndent.dll, I still get the same errors until I delete the nppAutoDetectIndent.dll subfolder. Then, it works without errors.

Please help me as I use NPP quite often and always with Auto Indent enabled.

Thanks,
Clem

[PeterJones]

@clem-patafio ,

As I answered here, you will have to contact the owner of the plugin (link provided in the other post) and ask them to fix the plugin to work with v8.3.

[Michael Vincent]

@peterjones said in Notepad++ v8.3 release:

@clem-patafio ,

As I answered here, you will have to contact the owner of the plugin (link provided in the other post) and ask them to fix the plugin to work with v8.3.

Issue opened - https://github.com/Chocobo1/nppAutoDetectIndent/issues/5

Cheers.

[Marcin Sawiak]

@peterjones
When I edit documents locally, it seems stable. But when I edit files remotely in WinSCP the problem comes back and the switch that you tipped over comes in handy. Thanks.

[Fantasyfr]

Hi folks,

i found a bug in the current x64 bit version of notepad++ the silent parameter for the directory relocation (/S /D=d:\otherfolder) does not work.
It is possible to fix this annoying issue?

Best regards,
Frank

[xomx]

@fantasyfr said in Notepad++ v8.3 release:

(/S /D=d:\otherfolder) does not work

Yes, mea culpa, I am just trying to fix that regression.

[donho]

FYI:
If you have somethings-else to say, speak out in Boycott Notepad++. All the subjects unrelated to bug/regression report of v8.3 will be delete and banned.

[Evgenii Filippov]

This post is deleted!

[Romain Bocquiau]

Notepad++ v8.3 installed.

When in PHP language, starting to write a command already known, it shows the list. if I see the autocompletion needed, i search with [ARROW UP/DOWN]+[ENTER].
i remember that before, the command was autocompleted.
now, it does a single “chariot return”.

for instance, i want to write “public $my_data;”
so let’s start … : “pu”

public is selected, so let press [ENTER]

why do we need to do [CTRL]+[ENTER] to get the same result ?

[PeterJones]

@romain-bocquiau ,

It was not Ctrl+Enter before: in previous versions, either the ENTER key or the TAB key would select the active choice from auto-complete. Starting in v8.2.1, the Developers added an option to configure whether it was ENTER or TAB or either (in Settings > Preferences > AutoCompletion); but because the option defaulted to TAB=on and ENTER=off, which changed the default behavior of Notepad++, it has confused a lot of users. You should go to that option, and ☑ ENTER, which will re-enable using ENTER to finish the auto-complete.

[Josh Davidson]

@peterjones Oh, thanks. I was confused because in config page it still showed “Enter” as the key to autocomplete, so I couldn’t understand what was going on. Well this behavior is great anyways, so I’m glad its staying.

[Eugene Philippov]

Great work, π do rust bl

[Hercules Queiroz Palombo]

@donho Using the latest release v8.3 the command line parameter -nLineNumber is not working anymore …
It open the file at the first line …
I’m using Windows 10 and notepad++ (x64) msi installer …
To reproduce go to de commando prompt e type notepad++ -n5 test.txt

[Michael Vincent]

@hercules-queiroz-palombo said in Notepad++ v8.3 release:

Using the latest release v8.3 the command line parameter -nLineNumber is not working anymore …
It open the file at the first line …
I’m using Windows 10 and notepad++ (x64) msi installer …
To reproduce go to de commando prompt e type notepad++ -n5 test.txt

Known issue . It will be fixed in the next version .

[PeterJones]

@michael-vincent said in Notepad++ v8.3 release:

It will be fixed in the next version.

which @Hercules-Queiroz-Palombo can confirm using the v8.3.1 Release Candidate

[Anderwriter]

As always, dude, thanks for all your work on this great editor!

Considering the many improvements in 8.3 (and 8.3.1), I don’t understand why v8.2.1 said “no update is available” when I checked from within it. Would more frequent auto-updates require too much bandwidth?

[Alan Kilborn]

@anderwriter said in Notepad++ v8.3 release:

Considering the many improvements in 8.3 (and 8.3.1), I don’t understand why v8.2.1 said “no update is available” when I checked from within it.

So this is a PERFECT example of exactly why it says no update is available.

8.3+ introduces HUGE file support, which caused a lot of new bugs to be introduced. Developers are working through the bugs, but probably at this point it isn’t a great idea for every single Notepad++ user out there to migrate to these versions. Just my 2c.

[Albrecht Hilker]

which caused a lot of new bugs to be introduced.

So why dont you release it marked as a beta version ?

[Alan Kilborn]

@albrecht-hilker said in Notepad++ v8.3 release:

So why dont you release it marked as a beta version ?

There are “release candidate versions”; click HERE and glance down the list produced, and you’ll see them.

[PeterJones]

@albrecht-hilker said in Notepad++ v8.3 release:

So why dont you release it marked as a beta version ?

Because this is the sequence that the developer usually follows:

0. Develop updates
1. Submit as Release Candidate (RC) version
2. Wait for feedback from those users who are willing to download a RC version
3. Iterate 1-2 until no “critical regressions” are reported
4. Release as official version
5. Wait for feedback from those users who are willing to download the released version without waiting for auto-update to be triggered (much larger number of people)
6. Do a faster loop back to step 1 if critical regressions found after #4
7. If no critical regressions found in #5, then trigger auto-update

The goal is for critical regressions to be found in #2 (the equivalent of “beta”), but not enough users download the RC/beta versions, so sometimes critical regressions are not found until #5. This happened to be one of those cases. Since the developer likes a fast-paced release cycle anyway, he feels that the current process works reasonably well – and the delay between #4 and #7 prevents “too many” people from downloading the release if a critical regression is found within a week or two of release.