@guy038 said: OR the options : Clear all marks, then mark all text and EOLs of the bookmarked lines Clear all marks, then mark all text of the bookmarked lines, excluding EOLs From my suggested Synchronize marks and bookmarks sub-menu ! Previously you suggested: So, most of the time, taking the line-breaks in account is not necessary ! However, adding the line-breaks characters is useful as it also includes the true empty lines ! Thus, this would simplify the Synchronize marks and bookmarks sub-menu to the following one : Bookmark only lines containing marked text Clear all bookmarks, then bookmark only lines containing marked text Bookmark visible lines Mark all text and EOLs of the bookmarked lines Clear all marks, then mark all text and EOLs of the bookmarked lines But then, just a moment ago, you wrote: Personally, after an Invert bookmarks action, I would expect a Mark only text in bookmarked lines action OR a Mark only text in bookmarked lines, excluding line endings action,as I explained in my last post ! so it sounds like you have changed your mind (unless I misunderstood your first suggestion) and believe users do need the ability to control whether line endings are included. The ideas at the front of my mind now are: Make Invert marked text a single command (no Invert sub-menu) which does only and exactly that one thing: mark every unmarked character and unmark every marked character. No bookmark changes, and no special treatment for line ending characters. Eliminate the “Bookmark first line of marked text” options. If you’re manipulating bookmarks based on marked text, trying to keep track of what is the “first line” is probably useless, confusing or both. (I still might remove that whole section of the Configure bookmarks dialog, too.) For the commands which Bookmark lines containing marked text, apply these rules: Lines containing only a line ending (empty lines) are bookmarked if the line ending is marked. Lines containing characters other than the line ending character(s) are bookmarked if any character other than the line ending character(s) is marked; the line ending is ignored. That third point is clumsy to explain (and certainly won’t fit in a menu item), but I think it makes synchronizing bookmarks to marks behave sensibly without introducing variants in either Invert marked text or [Clear bookmarks and] Bookmark lines containing marked text. I’m curious if you can think of situations where that would not behave as a user would expect. So, back to the situation where it’s the bookmarks that are primary, and you want update marks to follow bookmarks. I gather you do think it’s important to give the user control of whether line endings are included or not. Do you have specific cases or workflows in mind where each of these is useful? (I know, I’m the one that included the distinction in the first place, and now I’m trying to get rid of it if I can.) And/or perhaps there should be a separate option to expand marks to full lines (that is, if there is any marked text on a line, mark the entire line), with a choice to include or exclude line endings. There is also the possibility of turning Synchronize into a dialog instead of a sub-menu. That would allow for more options that could work separately or together without a huge menu of hard-to-read items, at the expense of slowing users’ workflow a bit more than a sub-menu. I’m still undecided; all observations and ideas are welcome.

@Paul-Adamczyk said: Still much to learn. Useful References: Notepad++ Online User Manual: Searching/Regex FAQ: Where to find other regular expressions (regex) documentation

@deleelee said: Can anyone tell me why the search result for line 9 displays only a single space after the asterisk instead a full tab space like all the other lines? I’m certain there is a tab after the asterisk in line 9 in the search results window. You can verify that by highlighting the asterisk through and including the following “A”, copying, then pasting that into your document (or a new tab). The visual results are a combination of the way tabs work in Notepad++ — so-called “typewriter tabs” — and using a proportional font. Tab stops are at fixed positions, spaced by the distance equal to the width of a chosen number of spaces in the font you’re using. (In document tabs, that number is chosen in Settings | Preferences… | Indentation | Indent size. However, regardless of that setting, in the search results window the number is always 4.) A tab character renders as a space of whatever width is needed to put the next character at the next tab stop. Notice that the colons after single digit and double digit line numbers don’t quite line up. That is because you are using a proportional font. Notepad++ adds a space to make up for the missing digit, and with a fixed width font, that would line them up. You are using a proportionally spaced font, and a space is not as wide as a digit; so the colons don’t line up. After the colon comes a space, then an asterisk, then a tab. The difference in placement of the colons happens to be just enough that the tab for lines with single-digit numbers finds the next tab stop at a different position than the tab in lines with two-digit numbers.

@PeterJones Thank you now as for my other questions …

@zdenko-s , I see pending pull request from 2022. Yep. It appears the owner @morbac hasn’t touched that repo since 2022. But the @epilogic-ch group at GitHub, which seems to be affiliated with @morbac, has made a couple of commits about a year ago, so it’s not completely abandoned. If repo is not maintained someone should take over maintenance. “take over maintenance” is not something that should be arbitrarily done. The code is GPL-3, which means anyone can use the code as long as giving credit to @morbac. But names of software projects are technically not part of the GPL-3. Names can be trademarked – registered or just effectively – and you cannot use the name without specific permission. (If you can show years of consistent use of a name as a “trademark”, even without using ™, then you can get and protect the “effective” trademark [IANAL, and I don’t know the legal term for a non-registered trademark]; XMLTools probably has enough history that the name is effectively trademarked to @morbac, but your interpretation and mileage may vary.) So, if you reach out and get permission from the current owner, you can definitely take over the code and name. (That’s been done with some plugins – sometimes, they even just give you commit-permission in the original repo, like was done for PythonScript). If they don’t respond or give permission, then another option is to fork the project, give it a new name, and publish it starting from the same codebase but under the new name (making sure to give proper attribution of where it was forked from). That’s happened, with a lot of the Markdown plugins in Notepad++. If you think you have the skills and the willingness to support the plugin under a new name, then great, go ahead and do that. But to just fork a repo, and then take over publishing under the original name is on legal/moral/ethical shaky ground, and I wouldn’t recommend it.

Feature request created: https://github.com/notepad-plus-plus/notepad-plus-plus/issues/18429 Put the several possibilities given my lack of knowing how the backend works and the feedback I’d gotten on this thread of possible feasibilities. I do stuff on both a Work computer using IT’s selected version of Notepad++ as well as home use, so even if I could get AutoIt working on my personal computer, I probably can’t get it running on my Work computer (permissions) I’ll try to train myself to alt+d

@rdipardo , I got a statement of sorts in regard to this request, specifically, this comment: Using AI to create a PR for an open source project - is it a good thing or a bad thing? I have no judgement on that. For me, the only criterion that matters is whether the merged code will be maintainable in the future. On this point, I have to say that AI-generated PRs (I can usually tell during code review), often do not meet the critera in their current state - but many human devs don’t either.

Thanks a lot @guy038 for running the whole thing again, this time it didn’t finish in seconds ;-) Nice to see the results panel still usable with almost 10 million hits, even the jump to line 690 in that DLL at the very end. Interesting that walking the whole drive for those 130 PDFs takes almost the entire run, 5m45 of 5m48 for MultiReplace, and it’s the same picture with the other tools. The 4 “not decodable” are most likely UTF-16 files with an odd number of bytes. N++ simply drops the last byte there, the next MultiReplace build will do the same in Find in Files (Replace leaves them alone, writing them back would lose that byte). Speed is next on my list.

Here are the latest binaries of SmartMath. This is a fully-working unofficial build that is going to be added to the official git repository… unless more improvements are suggested :) What’s new: the archive structure corresponds to the expectations of the Plugins Admin; the plugin searches for its documentation file near the SmartMath.dll, as well as in the “plugins\doc” folder; the plugin shows a warning when it does not find its syntax files in the expected locations under the “userDefineLangs” and “autoCompletion” folders of Notepad++. 64-bit version: https://drive.google.com/file/d/1pTS_cBdU_Q0vkG03cubqWZ9TDdYiSsXW/view?usp=drive_link 32-bit version: https://drive.google.com/file/d/1qsI5Hsx4XmyRlhVeGsplAoTX391WEnOv/view?usp=drive_link

@PeterJones Oh!! Understood!! thank you!!!

XBrackets Lite v2.0.4 Glory to Ukraine! Glory to the heroes! improved: a manually typed closing bracket steps over an auto-completed one, even after typing text inside the pair. For example, typing ( automatically inserts ), producing (|), where | indicates the caret position. Typing abc places the characters inside the pair, resulting in (abc|). Typing the final ) then steps over the existing ), resulting in (abc)| instead of adding a duplicate closing bracket (abc)). changed: while searching for “XBrackets.txt”, the plugin first checks the “plugins\XBrackets” folder, and only then checks the “plugins\doc” folder. a few internal corrections. https://github.com/d0vgan/npp-XBracketsLite/releases/tag/XBrackets_v204