This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: Command echo
- From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder at niaid dot nih dot gov>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Cc: "'Gluszczak, Glenn'" <glenn dot gluszczak at emc dot com>
- Date: Mon, 16 Nov 2015 16:40:46 +0000
- Subject: RE: Command echo
- Authentication-results: sourceware.org; auth=none
- References: <91DCAC3CB99C724EB365BB64677FBE7B01BE4B at MX204CL04 dot corp dot emc dot com>
Gluszczak, Glenn sent the following at Monday, November 16, 2015 11:16 AM
>
>When I shell to cmd.exe, the commands I execute are echoed (not sure if
>stdout or stderr). This doesn't happen under native cmd.exe. Is there a
>variable that controls this? I only have CYGWIN=nodosfilewarning
>
>Notice the commands "dir" and "whoami" are emitted to the output.
cmd.exe is in control of its own echoing. Try starting as cmd /q
cmd /?
...
/Q Turns echo off
...
As to why cmd behaves differently when started under bash (even in a
non-mintty window) than when started directly or under cmd ....
Hope that helps.
- Barry
Disclaimer: Statements made herein are not made on behalf of NIAID.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple