Notepad++ 7.6.1

dinkumoil

Could you confirm if this bug is fixed for you?

Where can I download a debug build of Notepad++? The AppVeyor build of the commit above and the commit before have failed, no artifacts available.

donho

@dinkumoil
It’s been fixed.
Otherwise you can download x86 release build here:
https://notepad-plus-plus.org/temp/notepadpp.zip

dinkumoil

@donho

Tested and it worked.

Jan Černosta

Since version 7.6, the ANSI code page is sometimes incorrectly detected. A file containing text “CHRÁNĚNÉ”, encoded in ANSI (Windows with the Czech Republic region selected, i.e. the Windows 1250 code page), is opened as “CHRÁNÌNÉ” (in both versions 7.6 and 7.6.1) with the automatically selected code page ISO 8859-3.

For file with more Czech letters (e.g. “ěščřžýáíé” at the first row) is ANSI code page selected properly, but text “CHRÁNĚNÉ” was also enough to select ANSI in 7.5.9 (and the older ones).

Some ANSI files (with Czech letters) are incorrectly opened in ISO 8859-2.

So far I have to stay on version 7.5.9, in which the ANSI code page is always selected correctly.

Besides this case, Notepad ++ is an excellent text editor.

Thanks, Jan

Ketrel

Any idea what I can do for this issue?
https://notepad-plus-plus.org/community/topic/16790/notepad-7-6-1/20

I cannot install any plugin. Any attempt just keeps trying to downgrade Notepad++ and never installs the plugin.

rinku singh

@Ketrel
Notepad++ v7.6.1 (32-bit)
Build time : Dec 12 2018 - 01:24:22
Path : C:\Program Files\Notepad++\notepad++.exe
Admin mode : OFF
Local Conf mode : OFF
OS : Windows 7 (32-bit)
Plugins : active text.dll DSpellCheck.dll mimeTools.dll NppConverter.dll NppExport.dll PythonScript.dll Remove dup lines.dll selectNLaunch.dll

you should expend the uac dialog capture and submit also.

Eko palypse

@Ketrel

haven’t had seen this before but could you check what happens if
you uncheck enable notepad++ auto-updater from
settings->preferences->misc dialog?
Maybe restart npp afterwards and try to install plugins.
If this doesn’t help would you mind posting the debug-info from ? menu?

Eko

rinku singh

@Ketrel
you have already got answer
https://notepad-plus-plus.org/community/topic/16790/notepad-7-6-1/35

unistall 7.6.1 and download new setup from
https://notepad-plus-plus.org

Ketrel

@gurikbal-singh said:

@Ketrel
you have already got answer
https://notepad-plus-plus.org/community/topic/16790/notepad-7-6-1/35

unistall 7.6.1 and download new setup from
https://notepad-plus-plus.org

Sorry, I completely missed that reply. That worked. I have no idea how I missed that reply o.O

Thanks @donho @gurikbal-singh @Eko-palypse

donho

@Jan-Černosta said:

Since version 7.6, the ANSI code page is sometimes incorrectly detected. A file containing text “CHRÁNĚNÉ”, encoded in ANSI (Windows with the Czech Republic region selected, i.e. the Windows 1250 code page), is opened as “CHRÁNÌNÉ” (in both versions 7.6 and 7.6.1) with the automatically selected code page ISO 8859-3.

Apparently the latest version of component uchardet doesn’t contain the fix of the regression:
https://cgit.freedesktop.org/uchardet/uchardet/commit/?id=26e1cebad15749a3aced87ff22fb18bf55dacd79

I’ll include this fix - could you test and validate the fix?

versat

I am using cntlm as proxy and it worked with Notepad++ versions before 7.6 without problems for years.
After updating from x32 version to 7.6.1 (x64) i get the following error:

---------------------------
curl error
---------------------------
Unsupported proxy 'https://127.0.0.1:3125', libcurl is built without the HTTPS-proxy support.
---------------------------
OK   
---------------------------

System:

Notepad++ v7.6.1   (64-bit)
Build time : Dec 12 2018 - 01:22:05
Path : C:\Program Files\Notepad++\notepad++.exe
Admin mode : OFF
Local Conf mode : OFF
OS : Windows 7 (64-bit)
Plugins : DSpellCheck.dll mimeTools.dll NppConverter.dll

dinkumoil

@versat

What did you do before that error message poped up? Installing or updating plugins? If yes, that would be something @donho should know.

versat

Sorry, because of the restrictions here i was not allowed to edit my post and i had to wait to add another one.

I finally found a corresponding issue on github for the curl https proxy problem:
https://github.com/notepad-plus-plus/notepad-plus-plus/issues/4602

I tried to update the DSpellCheck plugin, but it did not update. It stays the same version after Notepad++ restarts.
Since i guess that it has something to do with the proxy i tried to search for a Notepad++ update to check if it works there and received the curl https error message.

dinkumoil

@versat

I read your comment in the issue tracker and saw that you not only were able to solve your problem in the one or the other way but you were able to track down the error to its cause - something we see not often, unfortunately. Thumbs up!

RobertTanenbaum

Warning - Plugin Manager by Bruderstein is totally broken with the new 7.6.1 release of Notepad++ because now plugins are found in %PROGRAMDATA% (C:\ProgramData\Notepad++\plugins)
Make sure you use the Plugins Admin… and remove Plugin Manager until it is fixed.

Jan Černosta

@donho said:

@Jan-Černosta said:

Since version 7.6, the ANSI code page is sometimes incorrectly detected. A file containing text “CHRÁNĚNÉ”, encoded in ANSI (Windows with the Czech Republic region selected, i.e. the Windows 1250 code page), is opened as “CHRÁNÌNÉ” (in both versions 7.6 and 7.6.1) with the automatically selected code page ISO 8859-3.

Apparently the latest version of component uchardet doesn’t contain the fix of the regression:
https://cgit.freedesktop.org/uchardet/uchardet/commit/?id=26e1cebad15749a3aced87ff22fb18bf55dacd79

I’ll include this fix - could you test and validate the fix?

How?

donho

@KantorZsolt @Peter-Jones
Due to wingup has the retro-compatible issue with XP since its beginning, Plugins Admin will be disabled under XP. Sorry for that.

donho

@dinkumoil said:

Regarding APIs directory: As far as I know there are plugins wich are indeed lexers for a certain language. I actually found the WLangLexer which is part of the plugin list of old Plugin Manager. This plugin requests during its installation to copy an XML file to plugins\APIs.

I don’t use lexer plugins, thus I don’t know anything about them. But I think further investigations have to be done before making a decision regarding plugins and plugins\APIs directories.

Got your point, I’ll see what can I do for it.

Meta Chuh

@donho said:

Plugins Admin will be disabled under XP. Sorry for that.

no problem to drop xp … but i’d really like to hear @guy038 screaming “nooooooooo” ;-)

btw: thanks for today’s %PROGRAMDATA%\Notepad++\plugins permission commit

@dinkumoil
thanks again for testing everything, even the stuff you don’t use yourself.

regarding your suggestion at git to use %ProgramData%\Notepad++\autoCompletion instead of $INSTDIR\autoCompletion:

as those 3 plugins have to be rewritten anyways due to the path changes, is there any specific reason to use %programdata% instead of $instdir ?
as far as i can see the compatibility of those plugins will be broken anyways, regardless of using %programdata% or $instdir.
and the plugin authors can always put their own lexer files in their own plugins sub folder and use them from there.

@donho what’s your thought about that or prefered location ?
i think if those plugins that use lexer apis have to be rewritten anyways, they could just use the official autoCompletion as it is now, inside $INSTDIR\autoCompletion for read only, and use their own additional r/w lexer data files within %programdata%\plugins\theirplugin.

dinkumoil

@donho @Meta-Chuh said:

is there any specific reason to use %programdata% instead of $instdir ?

I thought of Notepad++ to be compatible with the UWP app requirements which means that the installations directory has to be immutable.

As far as I know the former APIs directory contains the autocompletion files for different languages. Maybe it is important that these files are stored at this location to ensure that Notepad++ uses them. So it would be the best to allow plugins to store files in this directory which means its location can not be in the installation directory.