Menu ▾ ▴

#355 COPY CON Unexpected message interferes with text input

freedos13
closed
Jim Hall
copy (1) con (1)
5
2022-02-23
2022-01-12
Anonymous
No

Unexpected message interferes with text input. The trivial solution is to overwrite the line. Apart from this minor bug the command fulfills its mission and the text can be saved successfully. Another comment: COPY CON does not seem to be documented in the HELP. Greetings.

1 Attachments

Discussion

  • Jim Hall

    Jim Hall - 2022-02-23

    issue 2: I have created a new Wiki entry for "CON:" that describes the behavior of hte DOS console (user input via the keyboard, or user output via the display)

    http://wiki.freedos.org/wiki/index.php/CON

    bug: fixed

     
  • Jim Hall

    Jim Hall - 2022-02-23

    issue 1: I was able to reproduce this behavior. You're seeing output from COPY displayed on stderr, but it's not actually input from stdin (CON). Here's my sample:

    D:\TEMP>copy con: t.txt
    con =>> t.txt
    aaaaaaaaaa
    aaaaaaaaaa
    copied 0KB/???KB
    

    and...

    D:\TEMP>copy con: t.txt
    con =>> t.txt
    aaaaaaaaaa
    aaaaaaaaaa
    zzzzzzzzzz/???KB
    zzzzzzzzzz/???KB
    ^Zpied 0KB/???KB
    D:\TEMP>type t.txt
    aaaaaaaaaa
    aaaaaaaaaa
    zzzzzzzzzz
    zzzzzzzzzz
    

    The "unexpected text" is a normal warning message from COPY that is being displayed. This isn't really a "bug" per se but confusion about a warning message.

    Marking as closed (not a bug). If you disagree and think this is a bug that needs to be addressed, please enter a new issue on GitLab.

     
  • Jim Hall

    Jim Hall - 2022-02-23
    • labels: COPY CON --> copy, con
    • status: open --> closed
    • assigned_to: Jim Hall
     
  • Jim Hall

    Jim Hall - 2022-02-23

    Marking as closed (not a bug). If you disagree and think this is a bug that needs to be addressed, please enter a new issue on GitLab.

     

Log in to post a comment.