New document | Default langauge not working for new NP++ instance

Craig O'Neil

Hi,

I’ve noticed that when I start a new instance of Notepad++ the “New 1” document isn’t set as HTML (my New document | Default language setting).

Works fine if I create a new document via File | New.

Seems like it’s started happening since v8.4.7 - just wondering if this is happening for others too?

thanks, Craig.

My debug info:

Notepad++ v8.4.7 (64-bit)
Build time : Nov 1 2022 - 23:31:11
Path : C:\Program Files\Notepad++\notepad++.exe
Command Line :
Admin mode : OFF
Local Conf mode : OFF
Cloud Config : OFF
OS Name : Windows 10 Enterprise (64-bit)
OS Version : 21H2
OS Build : 19044.2251
Current ANSI codepage : 1252
Plugins :
BetterMultiSelection (1.5)
DSpellCheck (1.4.24)
HexEditor (0.9.12)
HTMLTag (1.3.5)
mimeTools (2.9)
NppExport (0.4)
PythonScript (2)
QuickColorPicker (2.1.2.1)
XBrackets (1.3.1)

PeterJones

@Craig-O-Neil ,

Seems like it’s started happening since v8.4.7 - just wondering if this is happening for others too?

At first, I thought “it couldn’t be”. So I downloaded a fresh 8.4.7 , and followed the steps,

Settings > Preferences > New Document > Default Language = HTML
Close all open files (to make sure the session is empty)
Exit Notepad++
Run notepad++ again: the default new 1 is “Plain Text”, not “HTML”
Use File > New or equivalent, and new 2 is correctly “HTML”
Close new 1 and leave new 2 open
Use File > New or equivalent, and the newly-created new 1 is is also correctly “HTML”.
Close new 1.
Exit Notepad++
Run Notepad++ again: the default new 1 is “Plain Text”, not “HTML”

It appears I have confirmed your issue.

My guess is that it was introduced by the type-detection algorithm changes listed as number 11 in the v8.4.7 announcement

Please follow the instructions in our bug report FAQ to create an issue so that the developers can know there’s a problem. When you do, paste a link to your issue here in this discussion. Thanks.

PeterJones

@Craig-O-Neil ,

It was pointed out to me that there’s a high likelihood that you don’t have a GitHub account, and so cannot create an issue. Since I felt this was an important regression, I created issue #12586 for you. If you do have a GitHub account, or want to create one, feel free to add more description there if you feel I haven’t described it fully.

Craig O'Neil

@PeterJones thanks for all your help with this.
cheers, Craig.