bugGNU nano - Bugs: bug #59077, with Slang, nano does not resume...


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

bug #59077: with Slang, nano does not resume properly from a SIGSTOP

Submitter:  Benno Schulenberg <bens>
Submitted:  Mon 07 Sep 2020 04:38:25 PM UTC
Severity:  2 - Minor Status:  Fixed
Assigned to:  bens Open/Closed:  Closed

Tue 08 Sep 2020 03:04:38 PM UTC, comment #3: 

Fixed in git, commit dd24f6a1, by calling full-refresh() when a suspension was not invoked from within nano (when built with Slang -- ncurses handles all this perfectly fine).

Benno Schulenberg <bens>
Project Administrator
Tue 08 Sep 2020 10:47:09 AM UTC, comment #2: 

Bug existed since version 2.8.5.  The offending commit is 84ff9ebb: "don't let a SIGCONT write anything to the screen".

Well... an external SIGCONT causing confusing behavior is less important than resuming properly from an external SIGSTOP (with 'fg').

Benno Schulenberg <bens>
Project Administrator
Tue 08 Sep 2020 10:12:22 AM UTC, comment #1: 

(The issue with ^S not working after a suspension has been reported in bug #59078.)

Benno Schulenberg <bens>
Project Administrator
Mon 07 Sep 2020 04:38:25 PM UTC, original submission:  

To reproduce, configure nano with --enable-tiny and --with-slang, compile, and then run 'src/nano -z'.  Then, in a different terminal, do 'kill -SIGTSTP $(pidof nano)'.  Then, in the first terminal, type: fg <Enter>.  See that just "src/nano -z" is echoed and that the cursor sits below it.  Nano does not seem to have resumed.  But now type ^L.  The screen is restored.

Now type xxx ^W ^C ^R ^C ^O ^C, to check that nano is really working.  Now type ^S xxx ^S xxx.  Nothing happens.  Type ^Q.  Hopla, the six exes appear.  Somehow the terminal is not properly restored -- ^S halts the terminal output and ^Q resumes it, like on a real terminal.  But nano is supposed to have disabled those XOFF and XON keystrokes.

Anyway, now type ^X N.  See that the whole interface of nano stays on the screen, and the shell prompt sits on the second row.  This is confusing.  It would be better if nano cleared the screen upon exit (when using Slang).

These are two issues: ^L being needed to refresh the screen, and ^S not working after a suspension.  The second will need a separate report when the first is fixed.

Benno Schulenberg <bens>
Project 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
    2020-10-08 bens Open/ClosedOpen Closed
    2020-09-08 bens StatusIn Progress Fixed
    2020-09-08 bens StatusNone In Progress
        Summarywith Slang, nano does not resume properly from a SIGTSTP with Slang, nano does not resume properly from a SIGSTOP

    Back to the top

    Powered by Savane 3.9