tested with
$ uname -a
CYGWIN_NT-6.1 mOo-PC 1.7.27(0.271/5/3) 2013-12-09 11:54 x86_64 Cygwin
run the following code in .bat file, the file should be in GBK
encoding. as your system should be GBK encoding by default to parse
the batch file correctly
or copy paste the code to start->run
==[ to get a
On Mon, Dec 23, 2013 at 10:11:26PM -0500, Gerry Reno wrote:
>Is it possible to detect in an automated way when setup.exe has finished?
>
>Like some final file or marker?
I don't know for sure but you might be able to look at the output in
setup.log or setup.full.log.
--
Problem reports: htt
Is it possible to detect in an automated way when setup.exe has finished?
Like some final file or marker?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygw
> I am calling a few different .NET Framework 4.0 command line tools from
> Cygwin and have noted that .NET Framework 4.0 introduced a change that
> causes an incompatibility between it and Cygwin. I have carefully
examined
> .NET Framework 4.0 source code and also checked things out with an API
>
It was the BLODA -- fixed by disabling Avast, thanks a lot...
-- Irfan
On Mon, Dec 23, 2013 at 9:25 PM, Christopher Faylor wrote:
> On Mon, Dec 23, 2013 at 08:09:46PM +0100, Irfan Adilovic wrote:
>>On Mon, Dec 23, 2013 at 5:06 PM, Larry Hall (Cygwin) wrote:
>>> On 12/22/2013 9:09 PM, Irfan Adilov
On Mon, Dec 23, 2013 at 08:09:46PM +0100, Irfan Adilovic wrote:
>On Mon, Dec 23, 2013 at 5:06 PM, Larry Hall (Cygwin) wrote:
>> On 12/22/2013 9:09 PM, Irfan Adilovic wrote:
>>>
>>> On my 64-bit Cygwin installation, when I start `infocmp.exe` from
>>> within mintty, it opens up a new cmd-window (not
> > Check line 192 for a call to the WaitForAvailableConsoleInput function.
>
> I guess they expect hFile to be a console handle (which IS waitable).
>
> And my guess that they added the Peek intentionally to prevent the WaitFor
> call from slipping through (as we've seen it does, otherwise) on t
(apologies to the list; I accidentally sent this reply directly to Anton and
so his reply that he just sent will appear out of order on the list
archive).
Hi Anton,
Thanks for the response. Comments below...
> MSDN does not list pipe handles as waitable with WaitForMultipleObjectsEx
> (only a u
On Mon, Dec 23, 2013 at 5:06 PM, Larry Hall (Cygwin) wrote:
> On 12/22/2013 9:09 PM, Irfan Adilovic wrote:
>>
>> Hi,
>>
>> On my 64-bit Cygwin installation, when I start `infocmp.exe` from
>> within mintty, it opens up a new cmd-window (not mintty!), shows
>> options and immediately closes. However
> Check line 192 for a call to the WaitForAvailableConsoleInput function.
I guess they expect hFile to be a console handle (which IS waitable).
And my guess that they added the Peek intentionally to prevent
the WaitFor call from slipping through (as we've seen it does, otherwise)
on things that w
On 12/22/2013 9:09 PM, Irfan Adilovic wrote:
Hi,
On my 64-bit Cygwin installation, when I start `infocmp.exe` from
within mintty, it opens up a new cmd-window (not mintty!), shows
options and immediately closes. However, the infocmp process hangs in
a way that defies killing -- it cannot be kill
Wow, thanks so much to both of you! This is a HUGE help. I really
appreciate your time.
Take care,
Rich
On 12/23/2013 03:36 AM, Corinna Vinschen wrote:
> On Dec 22 21:55, Mikhail Usenko wrote:
>> On Sun, 22 Dec 2013 00:02:10 +
>> Winkel, Richard J. <...> wrote:
>>
>>> I have a hard time be
On Dec 22 21:55, Mikhail Usenko wrote:
> On Sun, 22 Dec 2013 00:02:10 +
> Winkel, Richard J. <...> wrote:
>
> > I have a hard time believing this is an unusual question but I swear
> > I've been googling everywhere without an answer! :)
> > I'm using rsync (under cygwin) to backup windows se
13 matches
Mail list logo
