@PeterJones

If you are using one of the built-in themes, you might try to compare your %AppData%\Notepad++\themes___.xml with the version from c:\program files\Notepad++\themes,

I don’t have a custom theme; I just use whatever existing themes and modify them (just two, really). I just replaced my %AppData% theme with the “program files” themes, and the colors look okay again.

795725ad-50a6-4d40-a0cf-308501ed7cea-image.png

But both your margins being light gray imply that your theme was missing both those definitions when you ran 8.8.9 for the first time.

I am pretty sure that when I installed Notepad++, I just copied the old saved themes over, which is why the new styles were probably missing.

In this screenshot, I set one to Bookmark to salmon and Change History to yellow, to make it obvious which was which.

This makes it much easier to understand. Thank you!

Update: See our Change History Margin FAQ, especially the “How do I change the size” section, for an example of how to change the size using PythonScript or NppExec. (But yikes, I see that FAQ is out of date, since it doesn’t show the ability to change the four colors, which was added years ago… I will have to fix that next)

I am not that ambitious, but I am sure the update will be appreciated!

Thank you again, Peter. Not only did your post help fix the problem, but it’s also educational and shows me how dedicated people are to Notepad++.

@PeterJones

Thank you, that’s very helpful. I’ll do that.

@Mark-Olson said in Menu command for ensuring current position is visible:

In general, the easiest way to do this is by typing any character and then reverting that change, but this very simple solution does not work if the current document is read-only.

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.

But obviously this is not happening. Instead the caret goes to nearst visible position without doing unfolding actions. My vote would be to change this behaviour, but changing it would possibly make some users unhappy which are used to use the arrow keys in the way they currently work.

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

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