Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#2 v2.5: \n doesn't do a \n\r on dos

closed-fixed
None
5
2006-04-18
2001-12-05
Anonymous
No

In the DOS DJGPP port, printw and other commands print \n as a newline without carriage return.
\n should be printed as \n\r on DOS.

Discussion

  • Mark Hessling
    Mark Hessling
    2001-12-16

    • assigned_to: nobody --> rexx
     
  • Logged In: YES
    user_id=27933

    Actually it should be \r\n (i.e., CR LF).

     
  • Logged In: YES
    user_id=27933

    This is the behavior if you've called nonl(). Without that,
    or with nl(), you'll get the CRLF. This is NOT specific to
    DOS, but applies to all ports. This is the designed
    behavior, although it differs from that of some other curses
    implementations. (I notice that the ncurses man page for
    nonl() seems to describe this behavior, though an actual
    test program linked with ncurses doesn't reflect it.)

    I'm open to further opinions on this subject, but for now,
    I'm marking it WONTFIX.

     
    • assigned_to: rexx --> wmcbrine
    • status: open --> pending-wont-fix
     
    • status: pending-wont-fix --> pending-fixed
     
  • Logged In: YES
    user_id=27933

    OK, I've revisited this issue. I can find no other existing
    implementation that behaves this way; nor is it described in
    the standard, which refers only to the effect on input. So,
    I'm changing the nonl() behavior to affect input only. The
    fix is in CVS now.

     
    • summary: v2.5: \n doesn't do a \n\r on dos --> v2.5: \n doesn\'t do a \n\r on dos
    • status: pending-fixed --> closed-fixed
     
    • summary: v2.5: \n doesn\'t do a \n\r on dos --> v2.5: \n doesn't do a \n\r on dos