@PeterJones said in ascii nfo sh problem dos2unix is required to fix the bash files!:

my guess is that it was v8.7.4 that changed that behavior.

Yep. If I have the cp437.nfo, if I open it in fresh (default options) for v8.7.3, it automatically opens it in OEM-US = CP437, and it looks right; if I open it in fresh v8.7.4, it autodetects as EUC-KR. Similarly, if I have the utf8.nfo, v8.7.4-and-newer will interpret it as UTF-8 bytes, so it is right… but if I open utf8.nfo in v8.7.3, it will open it as CP437, so it looks like junk.

Ok, I found that it was the “Change History Margin”… but when I made the “Background: Gray” then it made things worse… the current line of words now disappears:

2025-12-20-02-40-39_01.jpg

So I went into settings and changed the “Current Line Indicator” to “(*) Frame: Width=1” which is perfect:

2025-12-20-02-40-53_01.jpg

But, when I exit and restart NPP, the “Frame” setting does not “stick”…

2025-12-20-02-41-31_01.jpg

Can someone help me keep “Frame=On” active forever??

Updated linter++ to v1.0.2

This has mostly been concerned with changes to the dockable window with the results:

You can click on a column header to sort by that column You can drag the column headers to reorder the columns You can configure the font used for display

There’ve also been a few other minor improvements/fixes - see the Changes.md file

Downloadable from https://github.com/ThosRTanner/notepad-pp-linter/releases if you can’t wait for the plugin list to be updated.

@deleelee said in Notepad++ 8.8.8: 2 issues detected:

So I guess it’s a decision between wanting shell icons on tabs or an unsaved changes indicator.

or the 3rd option - as I said, create new MenuIcons plugin GitHub issue and its author most likely fixes it and publishes a new compatible version

@xomx After restarting our Samba instance, the issues appear to be resolved. Apologies for the false alarm, but thank you for the responses!