bugGNU nano - Bugs: bug #13516, Flow control overruns trash files

 
 

bug #13516: Flow control overruns trash files

Submitted by:  None
Submitted on:  Thu 23 Jun 2005 01:23:39 AM UTC  
 
Severity: 3 - NormalStatus: None
Assigned to: NoneOpen/Closed: Closed

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Fri 24 Jun 2005 01:07:41 AM UTC, comment #2:

The version was 1.1.12 packaged with the Vector Linux distribution.

Upon downloading the latest source, the -p option has changed and now addresses the problem, allowing XON/XOFF flow control to work properly. The current version running with -p seems to fix the problem for us.

Thank you.

George Nemeyer <tigerwolf>
Thu 23 Jun 2005 07:01:00 PM UTC, comment #1:

>The terminal, as it should, sends an XOFF when its buffer is close to
>filling to avoid this, but nano is ignoring the flow control, and even
>displays "XOFF ignored, mumble mumble' in a hilighted box centered
>above the menu lines.
>
>Note that 'pico' does NOT have this problem and works fine.


Which versions of nano and Pico are you talking about? nano's been
ignoring XON/XOFF by default since version 1.1.99pre1, and Pico's been
doing it since the version that came with Pine 4.50. Both of them can
turn XON/XOFF handling back on via the "-p" command line option. nano
can also use the "--preserve" long command line option, or the "set
preserve" command in your .nanorc file, if you've compiled it with
.nanorc support. Do any of these fix your problem?

David Lawrence Ramsey <dolorous>
Project Administrator
Thu 23 Jun 2005 01:23:39 AM UTC, original submission:

When using a text serial terminal (DEC VT320 - yes there's lots still out there) with XON/XOFF flow control to edit a long file, scrolling down through screens of text causes garbage characters to end up in the file being edited.

This is due to the terminal's buffer being overrun because it takes extra time for the terminal to do cursor positioning and re-draw of the screen.

The terminal, as it should, sends an XOFF when its buffer is close to filling to avoid this, but nano is ignoring the flow control, and even displays "XOFF ignored, mumble mumble' in a hilighted box centered above the menu lines.

Note that 'pico' does NOT have this problem and works fine.

I've searched the archives (nano-devel mailing list search is broken, BTW) and the only reference to XOFF is an old comment saying it's being ignored after release 1.2.

Our application uses many such terminals, and with the hardware and wiring used, XON/XOFF is the only available choice for flow control since RTS/CTS isn't an option.

I'd like very much to use the interface-enhanced nano, but until this situation is corrected, it's not possible.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

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

Only logged-in users can vote.

 

Please enter the title of George Orwell's famous dystopian book (it's a date):

 

 

Follow 2 latest changes.

Date Changed By Updated Field Previous Value => Replaced By
Fri 24 Jun 2005 05:45:40 AM UTCdolorousOpen/ClosedOpen=>Closed
Thu 23 Jun 2005 02:18:35 AM UTCtigerwolfCarbon-Copy-=>Added -unavailable-

Back to the top


Powered by Savane 3.1-cleanup1