This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Executing Windows commands from Cygwin with or without cmd: what are the pros and cons?
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 4 Nov 2013 16:31:44 -0500
- Subject: Re: Executing Windows commands from Cygwin with or without cmd: what are the pros and cons?
- Authentication-results: sourceware.org; auth=none
- References: <CADex0xyCNo4QmZ=gDC0hz2o4if-TKuYFE-cN=HbBTRp0arMM_g at mail dot gmail dot com> <52780AD8 dot 3050904 at cygwin dot com>
- Reply-to: cygwin at cygwin dot com
On Mon, Nov 04, 2013 at 04:00:08PM -0500, Larry Hall (Cygwin) wrote:
>On 11/4/2013 3:35 PM, Kenneth Wolcott wrote:
>> Hi;
>>
>> Where can I find information regarding the pros and cons of using or
>> not using the cmd command to execute Windows commands from Cygwin?
>
>I think there would just be cons to using "cmd.exe" commands from within
>Cygwin. ;-) Obviously, this can end up being pretty subjective. But some
>of cons would be:
>
> o Doesn't understand PTYs (an issue when running a terminal like mintty)
> o Doesn't understand impersonation tokens used by ssh for pubkey
> authentication
> o Doesn't understand POSIX paths
> o Possible namespace/functional overlap and/or collisions
>
>Many of these can be worked around in one way or another but that's not
>enough to move them out of the "con" category. ;-)
One con is that cmd recognizes "con" as a device rather than a filename...
--
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