Re: [Bug-wget] Fwd: Re: [PATCH v3] bug #45790: wget prints it's progress even when background

2016-10-19 Thread Eli Zaretskii 
> From: "Wajda, Piotr" 
> Date: Wed, 19 Oct 2016 12:18:13 +0200
>
> For CTRL+Break we could probably go to background on windows by forking
> process using current fake_fork method. Child process should be then
> started with -c and -b.

Could be, although it'd be a strange thing to do for Ctrl+BREAK,
IMO, because it's akin to Unix SIGQUIT.

[Bug-wget] Fwd: Re: [PATCH v3] bug #45790: wget prints it's progress even when background

2016-10-19 Thread Wajda, Piotr 

Forgot to include mailinglist.

 Forwarded Message 
Subject: Re: [Bug-wget] [PATCH v3] bug #45790: wget prints it's progress 
even when background

Date: Wed, 19 Oct 2016 12:18:13 +0200
From: Wajda, Piotr 
To: Eli Zaretskii 

For CTRL+Break we could probably go to background on windows by forking 
process using current fake_fork method. Child process should be then 
started with -c and -b.


Piotr

On 19/10/16 12:12, Eli Zaretskii wrote:

From: "Wajda, Piotr" 
Date: Wed, 19 Oct 2016 11:57:06 +0200

My only confusion was that during testing on windows, when sending
CTRL+C or CTRL+Break it immediately terminates, which is basically what
I think it should do for CTRL+C. Not sure about CTRL+Break.


What else is reasonable for CTRL+Break?  We can arrange for them to
produce different effects, if there are two alternative behaviors that
would make sense.

Thanks.