Skip to content

Commit be4cbb1

Browse files
committed
Update changelog, help file and version info.
1 parent c82c2dd commit be4cbb1

3 files changed

Lines changed: 11 additions & 1 deletion

File tree

CHANGELOG.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,13 @@
11
# Search++: An enhanced search plugin for Notepad++
22

3+
## Version 0.2 -- March 27th, 2026
4+
5+
* Fix failure to reset `match` counter after a Replace All.
6+
* Add missing logic to make Replace Before and Replace After work properly after stepwise Find or Replace.
7+
* Remember the contents of the Find and Replace boxes between Notepad++ sessions. Sychronize Find and Replace box contents and all settings accurately when switching between the docking dialog and the non-docking dialog.
8+
* Add to the help file to clarify the special cases for Replace Before/After and what does and doesn’t reset the `match` counter. Correct broken links to this project on GitHub in the help file.
9+
* Fix some mistakes in the GitHub project setup: some ICU4C files that were needed were not included, and some that were not needed were included.
10+
311
## Version 0.1 -- March 25th, 2026
412

513
* First release. Still a work in progress.

help.htm

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -335,6 +335,8 @@ <h3>Search directions</h3>
335335

336336
</ul>
337337

338+
<p>There is an exception to the Before/After rules. If there is a single selection which is the result of an immediately preceeding stepwise find, or the find step of a stepwise replace, <strong>Replace Before/After</strong> <em>includes</em> the found text. This lets you do a series of stepwise replaces and then complete them with a Replace After (and for Plain text searches, the same with replacing backward and Replace Before).</p>
339+
338340
<h3 id="commands-scopes">Search scopes</h3>
339341

340342
<p>Search scopes determine what will be searched: <strong>Selection</strong>, <strong>Marked Text</strong> or <strong>Whole Document</strong>. The default is a “smart scope” which determines the effective scope based on whether there is already a selection or marked text in the document:
@@ -629,7 +631,7 @@ <h3>Replacement syntax</h3>
629631

630632
<p>Wherever a numeric value is used, it is also possible for the value to be <em>Not-a-Number</em>, an indication that something which was expected to produce a number failed to do so. This can happen because you tried to get a number from the document, but the associated text could not be unambiguously interpreted as a number. It can also be the result of an undefined mathematical operation, such as dividing by zero. In most cases, if any of the inputs to an operation or function are <em>Not-a-Number</em>, the result is also <em>Not-a-Number</em>. When the result of a formula is <em>Not-a-Number</em>, <strong>Search++</strong> does not insert any text, and no error message is provided.</p>
631633

632-
<p>Two special variables are defined. Use <code>match</code> to substitute a counter that begins at one for the first replacement and increases by one for each additional replacement. (Note that if you are using stepwise replacement, despite the name, the counter only counts <em>replacements</em>, not matches.) Use <strong>line</strong> to represent the line number in the document where the match begins.</p>
634+
<p>Two special variables are defined. Use <code>match</code> to substitute a counter that begins at one for the first replacement and increases by one for each additional replacement. (Note that if you are using stepwise replacement, despite the name, the counter only counts <em>replacements</em>, not matches. The counter continues through stepwise replaces, but resets after a Replace All or whenever the replace string is modified.) Use <strong>line</strong> to represent the line number in the document where the match begins.</p>
633635

634636
<h3>Format specifications</h3>
635637

src/resource.rc

0 Bytes
Binary file not shown.

0 commit comments

Comments
 (0)