search

aros-development-team / AROS

Main AROS repository for active development. Contains the main Operating System components and Build System.
http://www.aros.org
Other
384 stars 61 forks source link

Behavior of " RUN >NIL: " on CLI #83

Open ShK0 opened 4 years ago

ShK0 commented 4 years ago

Describe the bug When using >NIL: on CLI with RUN, it does not return back to CLI and prints an extra line [CLI 2] when all output should go into NIL.

To Reproduce Steps to reproduce the behavior:

  1. Go to 'AROS Early Startup Control'
  2. Click on 'Boot With No Startup-Sequence'
  3. Type in CLI 'run >NIL: date'
  4. Compare the behavior to Amiga OS 3.1

Expected behavior RUN >NIL: date should come back to the CLI and all output should go into NIL.

Screenshots RUN_NIL

Architecture

CPU

Version GID ID: b234335072

Additional context

wawatok commented 4 years ago

im posting a snippet of discussion here so that it is preserved: Kalamatee 13:19 @twilen i had a look but the code was ugly, and hard to figure out what should happen

twilen 13:19 shell is ugly and strange so thats normal for compatibility purposes..

Kalamatee 13:20 it looks like it is confusing things that should happen in the context of the caller with things that should be for the launched command

twilen 13:20 changing it back to standardoutput fixes the problem

Kalamatee 13:21 but is that correct? i dont understand why it has been output to stderror 13:21 (and havent invested time to look into the correct behaviour)

twilen 13:22 neither do i. It used stdoutput originally, when it was moved to shell, it mysteriously changed. I assume it was just a copypaste error or something.. (edited)

Kalamatee 13:23 sounds likely yes