@wonkawilly
All your posts will be removed.
Please post them on the other forums.
You will be banned if you keep posting non-critical issues here.

@mkupper said in Notepad++ v8.6.6 Release:

@Alan-Kilborn Thanks. I kept getting a zero length file via Firefox. I tried Edge. It hung for about 45 seconds but then downloaded and so I have the file. As it seems to be a glitch on my side I have deleted my original comment.

I can download both x64 portable packages (zip & 7z) without problem. I believe it’s the problem of cache from your side (browser/ISP).
You can try here : https://github.com/notepad-plus-plus/notepad-plus-plus/releases/tag/v8.6.6

@donho said in Notepad++ v8.6.6 Release Candidate:

Update to scintilla 5.5.0 & Lexilla 5.3.2. (Merge #15042 )

Thanks!!
This release fixes the long-standing issue with COBOL comments :
COBOL Comment lines are not displaying correctly if there is a character in Column 6

@Mr-Brunes said in Notepad++ release 8.6.5:

I assume this is related to this upgrade - apols if not.!

It’s not. Please create a new topic thread if you want to continue discussion on what you started here. But…start by reading the FAQ.

@Fruchtzwerg94 said in Notepad++ v8.5.5 :

@shridhar-singh Yes, this is most propably related to the discussion above. You can try to remove some plugins to the one who is responsible for that or just wait for the next Notepad++ release which fixes it.

in my windows 10, last version fixed this problem. you can upgrade to notepad.

Notepad++ v8.6.5 Release Candidate has just been updated from RC2 to RC3.

I apologize for repeatedly introducing fixes that may appear non-critical.
However, I’d like to draw your attention to a recent crash-fix related to the Shortcut Mapper:
A portion of the code within the Shortcut Mapper required modernization. This step is essential to prevent potential issues in the future. As part of this modernization process, a significant number of modifications were made during the RC2 phase. Given the importance of maintaining a stable application, I am prioritizing the completion of this task in the current release.

Sorry for any caused inconvenience and thank you for your understanding.

@vad-R ,

Bu trying older versions I found that this started after "Notepad++ 8.3.3 (Make Apps, not war) " - i.e. in 8.3.3 it does not crash, but in 8.4 and every later one it crashes in the same manner.

Thus, it is not a problem specific to the release of v8.6.4, and doesn’t belong in this discussion. The “Notepad++ release 8.6.4” Topic is only for issues that came about in v8.6.4 that didn’t exist in any version before v8.6.4.

I am using my moderator powers to make a copy of your post in the Help Wanted section – at https://community.notepad-plus-plus.org/topic/25557/notepad-crash-v8-4-through-v8-6-4 – where we can further discuss your particular issues before you make an official bug report. Please go there if you have anything more to say about this issue.

@rddim said in Notepad++ release 8.6.3:

There is no localization for
Make “copy/cut line while no selection” optional

There is. Please check:
https://github.com/notepad-plus-plus/notepad-plus-plus/blob/master/PowerEditor/installer/nativeLang/english.xml#L989

FYI, v8.6.3 RC2 binaries has been updated.
It fixes the problem of dark mode.

Notepad++ v8.6.3 Release Candidate 2:
https://community.notepad-plus-plus.org/topic/25478/notepad-v8-6-3-rc-2

@donho
Thanks a lot ,Thank you

@donho said in Notepad++ v8.6.2 Release Candidate:

I don’t think there is any other solution exists - that’s why NPPM_MODELESSDIALOG is there for this purpose.

But if you have the solution for it, you’re very welcome to do a PR. I’ll consider it for sure.

This GitHub message from plugin author @Mark-Olson led me to reconsider the idea. It would cause a change in behavior for plugins that currently have non-modal dialogs (including docking dialogs) and do not send NPPM_MODELESSDIALOG messages; it seems it is not safe to assume that change would always be welcome.

I described my “solution” here; but I won’t make a pull request, because I no longer think it is a good idea.

Hi friends,

I had no doubts about the Alan software.
But you answered well, and above all targeted my problem well.
This was not directly related to version 8.6.1.
But Sante doubts its update.
After investigation, I resolved the issue.
The software settings had been changed.
In particular FTP instead of SFTP, as well as port 21 instead of 22.
So everything is much better now.
Thank you for your answer.

Merci aussi mkupper

FYI, v8.6.1 RC binaries have been updated.
2 bug-fixes:

Fix deleting in column mode also delete an unexpected EOL Fix F4 not working for search result

@Mark-Olson said in Notepad++ v8.5.3 Release:

If anyone else is mildly (or severely!) dissatisfied with the fact that non-printing characters and control characters no longer show up by default, here is an issue that I introduced
and here is the script that I created to show non-printing and control characters but not CR and LF:

from Npp import * notepad.menuCommand(44130) # toggle all non-printing characters notepad.menuCommand(44131) # toggle all control characters (e.g., BEL, ENQ)

I’ve done something similar, using the Customize Toolbar plugin to create a custom button:

View,Show Symbol,Show Control Characters Unicode EOL,,*#4080C0:¶,*#4080C0:¶

Note the two spaces between “Show Control Characters” and “Unicode EOL” and no ampersand![^1]

custom_button.png

[^1]: I spent a lot of time on this until I realised I could use the string from the Shortcut Mapper.

It might have been nice to see a line item in the list of changes about the Direct Write setting now being defaulted to on for new installs.

@CennoxX said in Notepad++ v8.6 Release Candidate 2:

the black line is actually a bug in a plugin (CSVLint) in combination with the new version.

I know this issue had happened before with CSVLint in combination with ComparePlus in particular (and AFAIK ComparePlus has actually solved this problem on their end), but does the black-line bug now happen even without ComparePlus installed?

Big if true. If this is indeed the case, someone should definitely raise an issue in CSVLint’s GitHub repo.