bugGNU nano - Bugs: bug #61372, ^T^Z saying " Suspension is...

 
 

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

bug #61372: ^T^Z saying " Suspension is not enabled" is silly

Submitted by:  Benno Schulenberg <bens>
Submitted on:  Sun 24 Oct 2021 08:50:58 AM UTC  
 
Severity:  2 - Minor Status:  Fixed
Assigned to:  Benno Schulenberg <bens> Open/Closed:  Open

Fri 05 Nov 2021 02:35:29 PM UTC, comment #2: 

Revisited in commits d0c2c1e6 and 11fec6f6, 1) by letting ^Z not suspend nano but just tell the user to type ^T^Z instead (thus protecting the inexperienced user from the frustration of accidentally suspending nano), and 2) by letting the documentation say in various places to add 'bind ^Z suspend main' in a nanorc when the experienced user wants a single-keystroke Suspend.

Benno Schulenberg <bens>
Project AdministratorIn charge of this item.
Sun 31 Oct 2021 10:00:36 AM UTC, comment #1: 

Fixed in git, commit 83f94a88, by ignoring the -z and --suspendable options and enabling suspension by default.

Benno Schulenberg <bens>
Project AdministratorIn charge of this item.
Sun 24 Oct 2021 08:50:58 AM UTC, original submission:  

To see what I mean, run:

src/nano --ignore README

Then type: ^T ^Z
See that nano says "[ Suspension is not enabled ]" on the status bar.  This is frustrating.  If ^Z does not work in the Execute menu, then it should not be listed.  But the whole point of having ^Z in the Execute menu was to have it always available, even if the user rebinds ^Z in the main menu (to Undo, for example).

Expected behavior: ^T^Z should always work, regardless of the -z or 'set suspendable' options.  In fact, why have those options at all?  [...]  In the history of the nano-devel mailing list I cannot find any rationale for having ^Z disabled by default.  The two things I can think of are: 1) For Pico ^Z is an Unknown Command, so having it do something in nano might be unexpected?  2) Nano going to sleep and returning to the shell might confuse and bewilder inexperienced users: they might think nano exited and start nano again, and make the same edits again...

Maybe in the beginning nano did not give the helpful message about typing 'fg', but nowadays it does, and I think it is clear enough to not have to disable ^Z by default.  Vim and Emacs don't do that either.  And, if the user does tend to hit ^Z by accident (instead of ^X), then nowadays they can put 'unbind ^Z main' in their .nanorc to disable it -- no need for a special option, nor for a toggle, as they will still have access to suspension through ^T^Z.

Benno Schulenberg <bens>
Project AdministratorIn charge of this item.

 

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)
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

     

     

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2021-10-31 bens StatusNone => Fixed

    Back to the top


    Powered by Savane 3.7