Executing Windows commands from Cygwin with or without cmd: what are the pros and cons?
Larry Hall (Cygwin)
reply-to-list-only-lh@cygwin.com
Mon Nov 4 21:50:00 GMT 2013
On 11/4/2013 4:31 PM, Christopher Faylor wrote:
> 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...
Now Chris, don't con me!
--
Larry
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
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
More information about the Cygwin
mailing list