@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.

Notepad++ v8.6 Release Candidate 2 is available here:
https://community.notepad-plus-plus.org/topic/25158/notepad-v8-6-release-candidate-2

The regression of DEL is fixed in RC2.

@xomx
https://github.com/notepad-plus-plus/wingup/pull/48 is included.

Auto-update has been triggered for v8.5.8.

Binaries Update (again, sorry about that):
New updated binaries which contain the fix:
https://github.com/notepad-plus-plus/notepad-plus-plus/commit/8e43b0adbaed0353a7a97c2ff4e2da3e2dc8efa8

@donho said in Notepad++ v8.5.7 Release (Vulnerability fixes):

@imanubdesigner said in Notepad++ v8.5.7 Release (Vulnerability fixes):

It’s definitely something with the contextual menu, because if I use the portable version, which doesn’t insert anything into the contextual menu, everything works perfectly.

This crash of NppShell is fixed in v8.5.8 release. The candidate of v8.5.8 is available here:
https://community.notepad-plus-plus.org/topic/25015/notepad-v8-5-8-release-candidate

Could you check it and confirm here that the issue has been fixed?

I’m so sorry for delay of my reply. I can confirm that worked. This new 8.5.8 RC work perfectly in safe mode. I can’t see any refresh after right click. Thank you so much!

I am very sorry that my post did not follow the rules and style shaped by many forum predecessors.
I will delete that post I posted the day before yesterday.

Thank you very much for your guidance.
Thank you very much for the URL you provided, where I find an explanation of the issue I wanted to know.

Finally, Really, really, thank you very much.

@PeterJones said in Notepad++ v8.5.6 Release:

This topic, with 8.5.6 in the name, is specific to changes that came with 8.5.6. you should have started a new topic, not replied to the 8.5.5-specific discussion.

But really, as with joining any new forum, you should always check the FAQ list before posting, because:

Suppose we have recorded a macro on version v8.5.2 and …

FAQ exists on that question: v8.5.3 (and newer) Macros and Run-Menu Commands

A small update of new binaries:
Enhance “Convert case to Proper Case” command: fix the error conversion after quote:
https://github.com/notepad-plus-plus/notepad-plus-plus/pull/13584

Sorry for the inconvenience.

@Alan-Kilborn
Thank you so much for the advice: I have corrected my mistake deleting the wrong post and moving it to General discussion section here: https://community.notepad-plus-plus.org/topic/24713/enhancement-request-plugins-admin-dialog-transform-the-search-feature-like-the-one-into-shortcut-mapper-s-dialog-incremental-filter
Thank you again.

@David-Taylor I have the same issue after updating to NPP 8.5.4, please fix it.

@rddim
Could you check this PR please?
https://github.com/notepad-plus-plus/notepad-plus-plus/pull/13645

@Coises, @Alan-Kilborn, @PeterJones

Let me attempt to summarize, hopefully for someone’s benefit, what we know so far:

Problem 1: cryptic language identifiers in the Tab Settings list box

Cause: the window procedure that fills Tab Settings uses an instance of this Lang structure, which has a _langName member, filled by the name= attribute of langs.xml, which is identical to the Lexilla language identifier so that N++ can send it, unmodified, directly to Scintilla when creating the lexer (convenient for the developer, less so for end users).

Potential Solution: There is already a ScintillaEditView::_langNameInfoArray type with a more readable _shortName member. The approriate _shortName could be looked up using the enumerated _langID which every Lang instance already has; or else the Lang type can be refactored to store it’s own pretty name.

Problem 2: the first item, “[Default]”, is always selected in the Tab Settings listbox

Cause: the window procedure that fills Tab Settings does this on purpose by always passing a 0 index to the dialog window.

Potential Solution: the window procedure that sets the preference dialog needs access to an instance ScintillaEditView, which can look up the active lexer by calling getCurrentBuffer()->getCurrentLang(), then setting the index of the selected item appropriately.

Sound like fun? Well, that’s Win32 GUI programming in C++ for you.

FYI: it’s RC2 now.
It’ll be released in one day.

@Thomas-Böhmer
The context menu entry issues are fixed in v8.5.2. Please try v8.5.2 here and let us know if your issue has been solved:
https://community.notepad-plus-plus.org/topic/24328/notepad-v8-5-2-release-candidate

FYI
The new release will be based on RC2, which is more stable than other candidates are.

Thank you for your testing and report!

@User-Soft said in Notepad++ 6.8.4 released:

@donho said:

@User-Soft Tested in v6.8.4 under Windows 10 32bits, “hide in try” works for me.

Windows 7 64bits - not work.
6.8.1 - work hide in tray, 6.8.4 - not work.

Please check again Windows 7 64bits

Yes, it worked.