GNU nano - Bugs: bug #60667, something like +cr23 on the...
You are not allowed to post comments on this tracker with your current authentication level.
bug #60667: something like +cr23 on the command line does not get rejected
Submitter: | Benno Schulenberg <bens> | ||
Submitted: | Tue 25 May 2021 09:31:59 AM UTC | ||
Severity: | 2 - Minor | Status: | Fixed |
Assigned to: | bens | Open/Closed: | Closed |
Tue 25 May 2021 10:24:21 AM UTC, comment #2: |
Benno Schulenberg <bens> |
Tue 25 May 2021 10:03:25 AM UTC, comment #1: The commit that introduced +/ and +? is 2326bf69 from two years ago. It additionally makes the incorrect change from [1] to [n] in the call of parse_line_column(): when there is no / or ?, then nano should look at the first character after the +, and not skip any characters. |
Benno Schulenberg <bens> |
Tue 25 May 2021 09:31:59 AM UTC, original submission:
To reproduce, run
See that the cursor is on line 23. But "cr23" is not a valid line number. The "c" and "r" are only valid when they are followed by either "/" or "?". When not followed by either of those two, the whole ensemble should be ignored reported as invalid.
|
Benno Schulenberg <bens> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2021-06-16 | bens | Open/Closed | Open | Closed | |
2021-05-25 | bens | Status | In Progress | Fixed | |
2021-05-25 | bens | Status | None | In Progress |
Powered by Savane 3.13-4448.
Corresponding source code
Fixed in git, commit 8797ada8, by starting the number parsing at the first character after the + (when no / or ? was found).