Notepad3: .txt; .log etc. are NOT recognized as Text Files

[ltGuillaume]

None of the extensions listed for the "Text Files" scheme trigger a file to be recognized as such. Instead, all these files are shown with the scheme selected to be the default.

Notepad3 (64-bit) v5.19.815.2595
Compiler: MS Visual C++ 2019 v16.2.(0-2) (VC v1922)
OS Version: Windows 10 Version 1809 (Build 17763)
Locale: en-US (Codepage: 'ANSI (CP-1252)')
Scintilla v420
Oniguruma v6.9.3
UChardet v2018.09.27
TinyExpr v2018.05.11
UTHash v2.1.0

[craigo-]

Hi, @ltGuillaume -

Since early July 2019 (build 5.19.702.2382), a new Text Files scheme was introduced, to begin to treat "regular text files" in the same hierarchical way as any other scheme. The Default Text and 2nd Default Text schemes were then renamed to Common Base / 2nd Common Base around build 5.19.717.2395, to better represent that they are the base schemes from which every other scheme, including Text Files, is derived. The extensions formerly associated with the Default Text schemes were moved to Text Files, which became the default scheme. These changes became part of the current release you are testing.

You can find some discussion around this in issue #1425.

Edit: just had the thought that you might have migrated from a configuration file from an older version..? What happens when you use a brand new instance of Notepad3, e.g. the portable version? It should behave as described above.

[ltGuillaume]

I'm sorry, I was indeed comparing with Notepad2-mod, but I only called the scheme "Default Text" by mistake, instead of "Text Files". The bug, however, still persists. If you set any other scheme as default, txt; text; tmp; log; asc; doc; wtx; csv will NOT be opened with the Text Files scheme.

[hpwamr]

Could you please try with this beta "Notepad3Portable_5.19.831.2611_BETA" 🤔

• Simply extract the .7z file on your preferred place or
• Remove the ext .7z and use the installer paf.exe to install it on preferred place.
• See also #1105.

Feel free to test the BETA version "Notepad3Portable_5.19.831.2611_BETA" or higher.
See "Notepad3 BETA-channel access #1129" or download it from Notepad3Portable_5.19.831.2611_BETA.

[ltGuillaume]

OK, that was stupid, and very strange stuff. For some reason, the line FileNameExtensions=txt; text; wtx; log; asc; doc was added to the [Common Base] block.

I feel quite stupid for not noticing before, sorry about that. This possibly happened when updating to Notepad3 using the Notepad2-mod .ini file, but I cannot reproduce it now. The backed up Notepad2.ini file isn't the same as when I updated, though, so it's not the exact same situation anymore.

My apologies. case closed!

[hpwamr]

This possibly happened when updating to Notepad3 using the Notepad2-mod .ini file

Hello @ltGuillaume ,
If you compare Notepad3 with Notepas2-mod, be very careful because Notepad3 has followed its own path is no longer a duplicate of Notepad2-mod. 🤔

• Notepad3.ini is not the same as Notepad2(mod).ini
• Notepad3.ini has been deeply modified and is now "SettingsVersion=4"
• Notepad3.ini is no longer a "UTF-16 LE BOM" file but has become a "UTF-8 Signature" file !

[ltGuillaume]

Thanks for the info, you've been really helpful :-) :-)

Fortunately, it seems the file has been converted to "UTF-8 Signature" successfully and yes, I did notice the new SettingsVersion. If I run into any more issues, I'll be sure to check first if the same occurs with a new notepad3.ini file.

[RaiKoHoff]

@ltGuillaume : To be backward compatible, Notepad3 tries to read the [Default Text] settings from older Notepad3.ini files and pushes them to the New [Common Base], cause this section takes over the common base settings (which have been served by [Default Text] in prior versions).
Maybe we have a bug in this mechanism, cause it makes no sense, that [Common Base] section has a FileNameExtensions= key (it can not be edited through the dialog interface) :thinking:
Ed.: My tests show, that the former [Default Text] FileNameExtensions= are correctly transferred to the new [Text Files] section by backward compatibility mechanism :thinking:

[ltGuillaume]

Thanks for testing this. I came to the same conclusion when trying to reproduce, so the only thing I can think of is that it must've been either my own mistake, or a glitch when using IniSorter (by Grigsoft.com).