GNU nano - Bugs: bug #65204, when the linter command is...
You are not allowed to post comments on this tracker with your current authentication level.
bug #65204: when the linter command is "", running the linter messes up the input
Submitter: | Benno Schulenberg <bens> | ||
Submitted: | Wed 24 Jan 2024 11:52:13 AM UTC | ||
Severity: | 4 - Important | Status: | Fixed |
Assigned to: | bens | Open/Closed: | Open |
Fri 26 Jan 2024 10:17:07 AM UTC, comment #1: |
Benno Schulenberg <bens> |
Wed 24 Jan 2024 11:52:13 AM UTC, original submission:
To reproduce, run:
Now invoke the linter with: ^T^Y
|
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.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2024-01-26 | bens | Status | None | Fixed |
Powered by Savane 3.13-02a9.
Corresponding source code
Fixed in git, commit 88c8da14, by aborting the linter when the command string is empty.
The fix is improved in commit 0e72c0d3, by stripping leading blanks from that string first.