@Ryan-Cartmill

Your 1st log entry above means that the N++ file checking I/O routine succeeded within the specified maximum time limit (3 secs), but that the OS (or network layer) response is that the file corresponding to the opened doc/tab in the N++ was not found. (WIN32API Error Code: 2 means ERROR_FILE_NOT_FOUND). I also see that the file is named new 41 and without any path, so it looks like it’s not a real (saved) file yet(!?) but the newXXX N++ tab filebuffer only. But in that case the N++ getFileAttributesExWithTimeout call should not be used at all, as the N++ knows that it’s not a real file yet! Weird.

2nd one means that the OS (or network layer) doesn’t respond in the 3secs time limit at all.

@Charles-Fraichot

Glad you found a good solution. Thanks for letting us know.

OK, if it’s the intended behaviour then I’ll just live with it. It’s not a very big deal.

Thank you all who answered!

@Terry-R This has worked perfectly. Its a very long document so this was great. Thanks again, greatly appreciated.

@Mark-Olson said in Menu command for ensuring current position is 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.

After sleeping one night about it, and rereading your posting about typing any char and undo. Also in your issue #17297 and @Alan-Kilborn 's issue #12107 … I have changed my mind a bit, because I think that both situations of keystrokes (typing char from keyboard input or pressing arrow key) should be handled in the same way. This would make consistent behaviour of the application.

I think, keystrokes should always have direct effect on a visible caret, so the caret should be made visible first, and afterwards perform the action from keyboard (typing char/moving caret).

Keystrokes on an invisible caret look more like undefined behaviour. The user does not know, where his focus is. Even making caret jump to next visible position could be unexpected, because user did not know where he previously has been. Maybe user is even confused, because of the jump.

So from this perspective, the current behaviour of arrow keys could be worth considering if it is unexpected/inconsistent.

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

@Eric-Wiseman said in Bug in sorting lines, staying there for years:

Line Operations -> Sort lines works ONLY if you convert Edit -> EOL Conversion ->Unix.

Unless I am missing something this looks like a bug…

As others have already explained, this is not a bug but rather a known and documented limitation, that all line endings must be the same.

If Sort Lines In Locale Order Ascending and Descending do what you want, those sorts implemented differently and are not dependent on consistent line endings. The ending for each line will remain with the text of the line it follows.

The Locale sorts can also sort using a rectangular selection for the keys even if there are tabs or characters of differing byte widths (such as can happen with non-ASCII characters in UTF-8) to the left of the selection, which does not work with the other sorts.

@PeterJones

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

Thank you for all of the information. While it might be fun to dig into the Windows APIs again, I was hoping for something simple I could run with NppExec, etc. without a lot of coding. Since it’s not a lot of extra work to move the splitter manually, I’ll live with that for now. And maybe the MarkdownPanel team will find my request worth implementing, though it’s possible it can’t be done since one side is a NPP tab and the other is a panel.

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

New FAQ: https://community.notepad-plus-plus.org/topic/27306/faq-themes-in-v8-8-9

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

@Andrea-Gaviraghi

Yes we are seeing this in our Enterprise install testing of the MSI. We had to build a script to uninstall the executable and then install the MSI. And package the scrip & MSI in an Intune package. Seems to have solved the problem.

@rdipardo

This still worked for me a year later, thanks!