Post by Robert on Sept 4, 2023 12:01:34 GMT -5
While testing beta 23.246, I tried using the new , and . modifiers on C and issued a command of
f p'=' +red all
I was expecting characters in the line range to be changed to RED, but instead, the entire file was highlighted as RED.
Thinking it might be a bug in the currently added support for , comma modifier, I used C\ but the same result happened. Then I checked the current production 23.169, and the same thing happened.
I thought that when C/ or C\ was used on a line, it limited the primary command's actions to the subset of the file from that point forward or backward, but it seems like the / or \ is being ignored, in some cases.
I put C\ on line 2 and did a DELETE ALL command. Only the first 2 lines were deleted. So, it seems like the / or \ line-range option gets respected on a command by command basis. If so, this would call for checking all edit primary commands to see how this is being handled.
R
f p'=' +red all
I was expecting characters in the line range to be changed to RED, but instead, the entire file was highlighted as RED.
Thinking it might be a bug in the currently added support for , comma modifier, I used C\ but the same result happened. Then I checked the current production 23.169, and the same thing happened.
I thought that when C/ or C\ was used on a line, it limited the primary command's actions to the subset of the file from that point forward or backward, but it seems like the / or \ is being ignored, in some cases.
I put C\ on line 2 and did a DELETE ALL command. Only the first 2 lines were deleted. So, it seems like the / or \ line-range option gets respected on a command by command basis. If so, this would call for checking all edit primary commands to see how this is being handled.
R
