Notepad++ v8.3 release

Microka

@microka said in Notepad++ v8.3 release:
Update to v8.3(x64) from v8.2.1, open a file the cursor is positioned at the second character.
Not for me.

Could you please re-test with all your N++ plugins temporarily disabled?
(you can use e.g. this cmdline command with parameter “notepad++.exe -noPlugin” or simply rename your N++ subfolder “plugins” to “plugins.bak”)

I have renamed my N++ subfolder “plugins” to “plugins.bak”, and re-open a file but this problem still occur. Even i uninstall N++ and deleted user config files, and re-install N++ v8.3, still have this problem.

xomx

@microka
Please append here also your N++ Debug Info (N++ menu “?” -> Debug Info …)

Microka

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

@microka
Please append here also your N++ Debug Info (N++ menu “?” -> Debug Info …)

Notepad++ v8.3   (64-bit)
Build time : Feb  3 2022 - 03:39:05
Path : C:\Program Files\Notepad++\notepad++.exe
Command Line : 
Admin mode : OFF
Local Conf mode : OFF
Cloud Config : OFF
OS Name : Windows 11 (64-bit) 
OS Version : 2009
OS Build : 22000.434
Current ANSI codepage : 936
Plugins : none

Yaron

See https://github.com/notepad-plus-plus/notepad-plus-plus/issues/11128.

Sorry I didn’t find it a day earlier.

Vitalii Dovgan

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

Update to v8.3(x64) from v8.2.1, open a file the cursor is positioned at the second character.

I think it may be related to the file encoding (please specify is it ANSI, or UTF-8, or UCS-2) and to the exact characters in this file. Also it may have something to do with the system encoding for non-Unicode files.

Could you check if it is reproducible with a newly created file that contains e.g. just few first lines of your text in question? Could you share this file (either a new one, if the problem is reproducible there, or the original one, if the problem is reproducible only with it)?

Microka

@vitalii-dovgan N++ test files.zip
I create txt files with different encoding (including ANSI, UTF-8, UTF-8-BOM, UTF-16 BE BOM, UTF-16 LE BOM), all files reproduce this problem.

Vitalii Dovgan

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

I create txt files with different encoding (including ANSI, UTF-8, UTF-8-BOM, UTF-16 BE BOM, UTF-16 LE BOM), all files reproduce this problem.

I could not reproduce this problem using a fresh folder with just unpacked “npp.8.3.portable.7z” from https://notepad-plus-plus.org/downloads/v8.3/
Is it reproducible for you in the same situation?
If it’s reproducible, could you share your “session.xml” file?
If it’s not reproducible, could you try to identify what needs to be done to reproduce the problem? (Please note that the portable version does not use any additional plugin that might be previously installed for a non-portable version of Notepad++. In such case, the problem may be actually caused by some of plugins that were previously installed for a non-portable version. To test if it is so, you may rename the file “doLocalConf.xml” in your portable Notepad++ folder to make it non-portable).

Microka

@vitalii-dovgan said in Notepad++ v8.3 release:

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

I create txt files with different encoding (including ANSI, UTF-8, UTF-8-BOM, UTF-16 BE BOM, UTF-16 LE BOM), all files reproduce this problem.

I could not reproduce this problem using a fresh folder with just unpacked “npp.8.3.portable.7z” from https://notepad-plus-plus.org/downloads/v8.3/
Is it reproducible for you in the same situation?
If it’s reproducible, could you share your “session.xml” file?
If it’s not reproducible, could you try to identify what needs to be done to reproduce the problem? (Please note that the portable version does not use any additional plugin that might be previously installed for a non-portable version of Notepad++. In such case, the problem may be actually caused by some of plugins that were previously installed for a non-portable version. To test if it is so, you may rename the file “doLocalConf.xml” in your portable Notepad++ folder to make it non-portable).

It’s weird, using npp.8.3.portable.x64.zip cannot reproduce this problem. Even i rename the file “doLocalConf.xml”, still not reproducible.
I have renamed my N++ subfolder “plugins” to “plugins.bak” and deleted all files under “C:\Users[username]\AppData\Roaming\Notepad++”, the non-portable version still have this problem.

Now i figure out something. When i double-click a file to open it, this problem occur, but if i open a file using NPP’s menu “File -> Open” doesn’t have this problem.

Microka

It’s weird, using npp.8.3.portable.x64.zip cannot reproduce this problem. Even i rename the file “doLocalConf.xml”, still not reproducible.

To be clear, i am dragging a file to the portable NPP to test.

yakumo unr

NppTaskList 2.3 plugin (the latest) causes Notepad++ 8.3 x64 to shut down on start, including when the only file open is a new blank.
All other plugins I use seem to be fine, it’s probably down to the plugin author to update it but I thought I would report it in case others are struggling to find why the application is closing.

Michael Vincent

@yakumo-unr said in Notepad++ v8.3 release:

NppTaskList 2.3 plugin (the latest) causes Notepad++ 8.3 x64 to shut down on start, including when the only file open is a new blank.
All other plugins I use seem to be fine, it’s probably down to the plugin author to update it but I thought I would report it in case others are struggling to find why the application is closing.

Thanks - and please open a ticket on the appropriate place for that plugin (which seems to be here) and reference https://community.notepad-plus-plus.org/topic/22471/recompile-your-x64-plugins-with-new-header

xomx

@michael-vincent
NppTaskList probably here: https://github.com/Megabyteceer/npp-task-list

xomx

@microka
I am able to reproduce the problem now.

As you have already stated, it is visible only in an installed N++, not in a portable one. I can trigger this behavior e.g. by right-clicking on a text file and choosing “Edit with Notepad++” from the popup menu.

The previous 8.2.1 installation does not show this positioning on 2nd char.

xomx

@microka
Thanks for reporting that positioning at the 2nd char issue.

I have just submitted a PR, which will also fix this issue.

Microka

@xomx Thank you!

Yaron

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

As you have already stated, it is visible only in an installed N++, not in a portable one.

It can be reproduced with a portable NPP by using the command line: “NPP Path” “File Name”.

James Walker-Hall

auto-complete is broken in this release

Michael Vincent

@james-walker-hall said in Notepad++ v8.3 release:

auto-complete is broken in this release

It’s not. You just don’t read releases notes.

See here:
https://github.com/notepad-plus-plus/notepad-plus-plus/issues/11073#issuecomment-1020541332

Cheers.

James Walker-Hall

@michael-vincent ok well the new behaviour sucks

Michael Vincent

@james-walker-hall said in Notepad++ v8.3 release:

ok well the new behaviour sucks

Then change it back.