bugGNU nano - Bugs: bug #50080, [Wish] add a configure option to...


You are not allowed to post comments on this tracker with your current authentication level.

bug #50080: [Wish] add a configure option to exclude the linter code

Submitter:  Benno Schulenberg <bens>
Submitted:  Wed 18 Jan 2017 08:48:53 PM UTC
Severity:  1 - Wish Status:  Fixed
Assigned to:  bens Open/Closed:  Closed

Wed 16 Nov 2022 08:07:45 AM UTC, comment #4: 

Released in nano-7.0.

Benno Schulenberg <bens>
Group administrator
Mon 29 Aug 2022 02:43:29 PM UTC, comment #3: 

Fixed in git, commit 6243831d, by adding --disable-linter and --disable-formatter to the configure.ac file.

Benno Schulenberg <bens>
Group administrator
Mon 14 Mar 2022 11:11:56 AM UTC, comment #2: 

The spell checker shifted to ^T^T (or ^T^S, if one prefers), and the formatter and linter have their own shortcuts, M-F and M-B (or ^T^O and ^T^Y).

Still, for people who want a smaller nano (but don't want --tiny, because they want undo and text selection and such), it would make sense to have a --disable-linter and --disable-formatter, just like we have a --disable-speller.

Benno Schulenberg <bens>
Group administrator
Tue 07 Mar 2017 11:41:48 PM UTC, comment #1: 

i'm not sure a configure flag is the best route here.  maybe we should keep ^T as the spell checker, and add new shortcuts for linting/formatting.  i often want to run a spell checker on my source files (like comments), and getting a linter instead kind of sucks :).

Mike Frysinger <vapier>
Group Member
Wed 18 Jan 2017 08:48:53 PM UTC, original submission:  

The linter is quite a block of code, and I can imagine that some people don't like it that ^T ever does anything else than spell checking.  And currently only four syntaxes define a linter, so its out-of-the-box usefulness is very limited.  (And in addition, the linter for shell scripts doesn't seem to do anything useful; the Python one maybe a little; and the other two I don't need because never use those languages at all.)

Furthermore, for some files, running a linter costs quite a bit of time, during which nano is blocked.  It has happened several times that I have accidentally typed ^T on a C file (where I have a linter defined for testing purposes) and then had to wait several seconds for the lint checker to finish.  :|

So... it would be nice to be able to disable that thing completely.

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 vapier (Posted a comment)
  • -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.


    Follow 6 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2022-11-16 bens Open/ClosedOpen Closed
    2022-08-29 bens StatusIn Progress Fixed
        Summary[Wish] add a configure option to --disable-linter [Wish] add a configure option to exclude the linter code
    2022-08-28 bens StatusNone In Progress
        Assigned toNone bens
    2022-03-14 bens Summary[Request] add a configure option to --disable-linter [Wish] add a configure option to --disable-linter

    Back to the top

    Powered by Savane 3.12