@Jayson-Allen ,

See details in https://community.notepad-plus-plus.org/post/104192

update: I have versions of the theme files which won’t have the ugly white backgrounds temporaroly at https://github.com/pryrt/notepad-plus-plus/tree/themesPost889/PowerEditor/installer/themes ⇒ they will hopefully eventually be put into the main codebase, for distribution with v8.9 and future. But until then, you can

Exit Notepad++ Go to that URL and download the raw version of your theme(s) For a normal Notepad++ installation, use Explorer to go to %AppData%\Notepad++ if there’s not a themes subdirectory, create it move the downloaded theme(s) into %AppData%\Notepad++\themes When you run Notepad++ next time, it will use the updated theme.

If you have customized your theme with user-keywords or user-extensions, this would overwrite those… I will eventually be writing a FAQ which explains a way to work around those customizations (once I don’t have to link to a branch in my fork of the code to share the theme files).

Since nobody here has indicated strong disagreement with my position, I’ve created an issue in the GitHub repo asking for this feature.

@MarkusBodensee said:

My expectation for the scenario would be, that using the arrow keys to move the caret, would also unfold and make the current position visible.

I agree with you that this is pretty confusing, and agree that using the arrow keys should have the same effect as typing. This would obviously be a separate feature request though, and as you noted I rather doubt that it would be accepted because it would only add confusion for some other users.

@deleelee

Thanks for the pic. You are evidently using the MenuIcons plugin and it seems that this plugin has a problem with the N++ v8.8.8+ new tab-label length limitation feature. You can try to report/ask for help at that plugin site:
https://github.com/francostellari/NppPlugins/issues

or disable its “*” tab marking feature in the Menu Icons Options settings (select the “No symbol” radio-button there).

@Adam-Sr-Flores

The simplest workaround here is to disable the N++ file-status checking in the Preferences > MISC. > File Status Auto-Detection (select Disable there).

My guess is that either something has recently changed on your remote server (e.g. a networking/caching setting) or you’ve started to experience occasional network connection outages. If you have the File Status Auto-Detection set to its default (Enable for current file), whenever an opened tab in N++ gets activated (switched to), N++ v8.7.1+ issues a threaded (to prevent a possible frozen app state) I/O checking call. As of now, if your server isn’t able to respond in time (3 secs), the checking thread is then forcibly terminated and one can experience such behavior described in your report. I’d like to improve this in the future (e.g. with an adjustable timeout limit), but unfortunately haven’t had time to do it yet.

Could you follow these instructions and paste here the nppLogNetworkDriveIssue.log obtained?