Hello @offshore9521 and All,

Humm…, @offshore9521, there are two separate problems with your regex !

From your INPUT text :

Your regex (?<![\.\!\?])\r\n([a-z]) means :

If a \r\n sequence, followed with a letter (a through z), is not preceded by :

A dot

An exclamation mark

An interrogation mark

Then rewrite this letter

BTW, you can shorter this regex as (?<![.!?])\r\n([a-z])

But, the ’ character is not a character of the [.!?] list. Thus, this explains why your regex merges the lines 1 and 2

Now, I suppose that your true goal was : if a line is not a true sentence, then merge that line with the next one with a space character ? This lead to the following regex S/R :

FIND (?<![.!?’])\r\n(?=\w)

REPLACE \x20

So, any \r\n sequence, which respects the before and after conditions, is simply replaced with a space character

Notes :

As you see, I included the ’ character within the list of the forbidden chars, in the negative look-behind

I used \w, which is identical to the [\u\l\d_] class character, instead of [a-z] to not bother about case !

Remark :

FIND (?<![.!?’\r\n])\R(?=\w)

REPLACE \x20

Best Regards,

guy038

P.S. : As an exercice, try to understand why the following regex S/R does not work as expected :

FIND (?<![.!?’])\R(?=\w)

REPLACE \x20

To help you, don’t forget to click on the ¶ icon of the Toolbar !

Hi @Clicketyclick,
I’ve updated DoxyIt and tested it on my x64 machine.
Please give it a try: https://github.com/AN-2101/DoxyIt/releases/tag/v0.4.5

@prof-tech said in Can't get the old toolbar:

Help! I have tried everything to get the old toolbar and it doesn’t appear! can anyone help me?

Settings > Prefernces > Toolbar: the “Fluent UI” variants are the “new toolbar” and “standard icons: small” are the “old toolbar” (and the “Hide” checkbox turns it on and off)

@Alan-Kilborn said in 'Find in Files' doesn't appear to work:

If a folder doesn’t exist, I think when the search is initiated, input focus will immediately jump to the Directory: box, signaling a problem with that folder to the user (without a message box). Not on a PC right now, so can’t verify; going from memory.

I see you are correct. However… I also see that the search results show 0 files searched. So I don’t see how it could be a problem with what is in the Find box. The directory might exist, but not be the one OP meant to search.

Hello, @brenda-gross-0 and All,

Very easy with regexes !

Open the Replace dialog ( Ctrl + H )

Un-tick all box options

FIND (?-i)(?<=\l)(?=\u)|_

REPLACE \x20

Tick the Wrap around option

Select the Regular expression search mode

Click, once only, on the Replace All button

Voila !

Notes :

The leading part (?-i) is an in-line modifier which force to take care about the case of letters, meaning non-insensitive search !

Then, due to the alternation symbol |, two individual regexes are performed, simultaneously :

(?<=\l)(?=\u) which searches for an empty string between a lower-case letter and an upper-case letter

_ which simply searches for the underline character

In both cases, the replacement changes the regex search with an normal space character \x20. I could have chosen to type a single space char, instead !

The regex search may also be expressed as a non-capturing group : (?-i:(?<=\l)(?=\u)|_), with the leading non-insensitive option

Best Regards,

guy038

@Charles-Fraichot

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

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

@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 temporarily at .../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

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

update 2: The installer themes in the source code have been updated to have all the styles needed (to be able to fix the problems from v8.8.9). You can go here to grab the theme file(s) you want: https://github.com/notepad-plus-plus/notepad-plus-plus/tree/master/PowerEditor/installer/themes

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

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

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

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!

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.

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