bugGNU nano - Bugs: bug #51357, in the help lines, ^T does not...

 
 

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

bug #51357: in the help lines, ^T does not adapt to the file type

Submitter:  Benno Schulenberg <bens>
Submitted:  Sun 02 Jul 2017 07:57:25 AM UTC
   
 
Severity:  3 - Normal Status:  Fixed
Assigned to:  bens Open/Closed:  Closed

Sun 02 Jul 2017 06:17:29 PM UTC, comment #2: 

Fixed in git by commit 7d46eff7.

(That it showed the wrong text wasn't so bad, but ^T didn't do the right action either, and that was bad.)

But... that no one complained since 2.6.1...  It seems to show that very few people use the linter.  Or at least: that very few people use the linter and edit files of different types at the same time.  (Which makes sense: when you're linting, you're probably concentrating on a certain type of file.)

Benno Schulenberg <bens>
Group administrator
Sun 02 Jul 2017 11:49:00 AM UTC, comment #1: 

The original offendig commit is 9106cc8e.

Benno Schulenberg <bens>
Group administrator
Sun 02 Jul 2017 07:57:25 AM UTC, original submission:  

To reproduce, run:

  src/nano  README  /usr/lib/python3*/random.py

The README file does not match any syntax, so the default syntax applies, and the random.py file should be governed by the python syntax, which defines a linter (pyflakes).  So when I now switch buffers from README to random.py, I expect "^T To Spell" to change to "^T To Linter".  But it doesn't.

When specifying the two files in reversed order, then ^T will continue to say "To Linter" also when we switch to the README file (and even when we close the Python file).

Bug exists since nano-2.6.1.

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 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2017-07-22 bens Open/ClosedOpen Closed
    2017-07-02 bens StatusNone Fixed

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code