bugGNU nano - Bugs: bug #47207, some rcfile errors are never shown

 
 

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

bug #47207: some rcfile errors are never shown

Submitter:  Benno Schulenberg <bens>
Submitted:  Sat 20 Feb 2016 04:30:42 PM UTC
   
 
Severity:  2 - Minor Status:  Fixed
Assigned to:  bens Open/Closed:  Closed

Sun 28 Feb 2016 08:52:25 PM UTC, comment #1: 

Fixed in SVN, r5696 -- disallowing to continue adding to a syntax that was defined in another file, and after an invalid syntax command.

Benno Schulenberg <bens>
Group administrator
Sat 20 Feb 2016 04:30:42 PM UTC, original submission:  

Things like "Cannot add a color command without a syntax command" the user will never see, even if she starts her .nanorc with something like 'color green ".*"'.

This is because Debian (and probably other distros) include several or all syntax files in their /etc/nanorc file, so by the time nano starts to read the user's .nanorc file, it has already seen a 'syntax' command, and will continue to add to the last one.  On my system the last syntax it has seen is the default one.  So when I start my .nanorc with the line 'linter oops!'. in any file that does match any syntax ^T will run not the spell checker but will try to run 'oops!'.

What should happen is: whenever nano leaves an include file, or any rc file, it should forget that it has seen a syntax command.  Or at least: it should not allow to continue adding or changing things in whatever was the last syntax to be defined.  (The extendsyntax command is available for doing that explicitly.)

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.

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2016-06-20 bens Open/ClosedOpen Closed
    2016-02-28 bens Severity3 - Normal 2 - Minor
        StatusNone Fixed
        Assigned toNone bens

    Back to the top

    Powered by Savane 3.13-f8d8.
    Corresponding source code