Odd Issue

Drxenos · Post by **Drxenos** » Mon Dec 15, 2014 5:33 pm

I've noticed an odd issue with the latest TextPad (maybe be in older versions, but I've never noticed it before). I don't know if it's by error or design. If I perform a regular expression on a selected set of lines, and if the line following the selection is empty [i.e., contains just a end-of-line character(s)], the expression will also be performed on that line. If the following lines is NOT empty, the expression will not be performed.

For example: If I use the find expression "^.*$" with the replacement expression "//$&" to comment-out the selected lines for C or C++, it will also comment-out the line following the selection, if and only if, it is blank.

It's not a big deal, but an oddity.

DrX

ben_josephs · Post by **ben_josephs** » Mon Dec 15, 2014 6:53 pm

Yes, this is a bug.

Your regex replacement is more complex than necessary. This has the same effect:

Find what: ^
Replace with: //

except that it doesn't suffer from the bug you've reported.

Drxenos · Post by **Drxenos** » Tue Dec 16, 2014 8:33 pm

Thanks. I never knew you could just match anchors.

ben_josephs · Post by **ben_josephs** » Tue Dec 16, 2014 11:36 pm

Regexes match strings. An anchor is a regex that matches a zero-length string in some specific context (such as the beginning of a line).

Ryck · Post by **Ryck** » Fri Feb 13, 2015 8:18 pm

ben_josephs wrote:Regexes match strings. An anchor is a regex that matches a zero-length string in some specific context (such as the beginning of a line).

My case is different. I often have to add to the row either by prefixing something or suffixing something to the row. Examples:

^
IM,

or

$
,D

Textpad always processes these commands on the last blank line. I've simply remove the last line but I would prefer it not behave in this way. This is a bug.