bugGNU 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: 

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.

Benno Schulenberg <bens>
Group administrator
Wed 24 Jan 2024 11:52:13 AM UTC, original submission:  

To reproduce, run:

echo 'syntax one ".*"' >smallrc
echo 'color blue "the"' >>smallrc
echo 'linter ""' >>smallrc
src/nano --rc=smallrc README

Now invoke the linter with: ^T^Y
Nano says it "Got 0 parsable lines from command:  ".

Now try to exit from nano with: ^X
The character gets printed verbatim.
Try to move the cursor left: ^[OD gets printed.  :/
Something is quite wrong.

Escape with: ^Z fg <Enter> ^X

Problem exists since commit bc36813349 from three years ago.  Before that, nano would crash when invoking the linter while the command was empty.

Benno Schulenberg <bens>
Group administrator


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by bens (Submitted the item)

    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 StatusNone Fixed

    Back to the top

    Powered by Savane 3.13.
    Corresponding source code