However, after assuming that developers are smarter than I am, i found it.
In XP I would have zero problems, but I was using Seven! I created a
per-user variable "CYGWIN" thinking that it will be visible to all
programs.
But operating system thinks otherwise - per-user variables only affect
progr
I can give more information but I just do not know what else to say.
Everything else except CYGWIN variable is unchanged since
installation.
2014-09-23 10:52 GMT+04:00, Пётр Б. :
>>I hope you aren't using 32-bit tools to view environemnt of 64-bit
> applications, do you?
>
> I am not. I see the ar
Пётр Б. wrote:
I was frustrated by not being able to view CMD of Cygwin processes in
Windows tools. After a bit of research I found the talk about the
wincmdln option and saw it mentioned in changelog.
However, setting it did not take any effect even after reboot,
Windows 7 SP1 Prof x64, Cygwin
>I hope you aren't using 32-bit tools to view environemnt of 64-bit
applications, do you?
I am not. I see the argv[0] in ProcExp64 - executable name - and nothing more.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: h
I was frustrated by not being able to view CMD of Cygwin processes in
Windows tools. After a bit of research I found the talk about the
wincmdln option and saw it mentioned in changelog.
However, setting it did not take any effect even after reboot,
Windows 7 SP1 Prof x64, Cygwin 1.7.32.0274 x86_
5 matches
Mail list logo
