bugGNU nano - Bugs: bug #49723, [Request] allow the user to quit...

 
 

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

bug #49723: [Request] allow the user to quit Nano immediately when multiple files are open

Submitter:  Yuval Khalifa <iyuvalk>
Submitted:  Mon 28 Nov 2016 08:54:21 AM UTC
   
 
Severity:  1 - Wish Status:  Wont Fix
Assigned to:  None Open/Closed:  Closed

Tue 29 Nov 2016 11:55:43 AM UTC, comment #3: 

Under ncurses (what nano uses), Ctrl+Letter and Ctrl+Shift+Letter produce the exact same code (which you can verify by pressing Alt+V before them).  This is a major reason why nano is rather limited in the number of shortcuts it can provide.

The mentioned two editors are ones with /lots/ of features, and are both graphical too -- they are in a different league from nano.  (And the first one isn't even free software, so it doesn't count. :) )

Benno Schulenberg <bens>
Group administrator
Mon 28 Nov 2016 08:12:40 PM UTC, comment #2: 

Hi.

Thanks for the quick reply. I understand your POV but since most modern editors (such as UltraEdit and Notepad++) do have a "Close All" option I thought it would be nice if Nano had that too. Also, I think that it would make it easier to use in cases which Nano plays a part in a bigger script that at some point allows the user to open multiple config files with Nano and instead of having to hold Ctrl+X until it's closed just press a key combo would be better. As for the fact that there are no keys left - how about Ctrl+Shift+X?


Yuval Khalifa <iyuvalk>
Mon 28 Nov 2016 06:44:03 PM UTC, comment #1: 

Hmmm...  I don't see what advantage such a Close-All function would bring.  Pressing and holding Ctrl+X works just fine -- I've just tried it with /hundreds/ of files open.  The only tiny advantage that Close-All would have is that, when you have modified several of the open files, you don't have to type ^X again after saying Y or N to the question about saving a modified file.  But the user should have learned to save his or her changes before switching to another file, so this question should pop up almost never.  So... holding down ^X works fine for me.

Also, we don't have any reasonable key to assign Close-All to: Meta-X is already taken, and so are all other sensible keys.  The only (but counter-intuitive) option would be to add this Close-All function to the ^O (Write Out) menu...  But, as said above, I don't see the need for it.

Benno Schulenberg <bens>
Group administrator
Mon 28 Nov 2016 08:54:21 AM UTC, original submission:  

Currently, if a user opens Nano with multiple files as arguments (e.g nano /tmp/*.txt) if the user hits ^X (Ctrl+X) Nano will close the current file and switch to the next file. I believe it would be better to allow the user (perhaps by using a different key combo, maybe Meta+X) to close all the files (if some have unsaved changes to ask the user about them) and quit.

Yuval Khalifa <iyuvalk>

 

(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 (Posted a comment)
  • -email is unavailable- added by iyuvalk (Submitted the item)
  • -email is unavailable- added by iyuvalk (NANO_CLOSE_ALL)
  •  

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

    Date Changed by Updated Field Previous Value => Replaced by
    2017-02-24 bens Open/ClosedOpen Closed
    2016-11-28 bens Severity3 - Normal 1 - Wish
        StatusNone Wont Fix
        SummaryAllow the user to quit Nano immediately when multiple files are opened [Request] allow the user to quit Nano immediately when multiple files are open
    2016-11-28 iyuvalk Carbon-Copy- Added -email is unavailable-

    Back to the top

    Powered by Savane 3.13-3230.
    Corresponding source code