On Wed, 16 Dec 2015, Dan Fandrich wrote:

> The --next option opens up the possibility of adding a feature to do this.
> Essentially, curl would parse options up to the --next, fire off the transfer,

Right. Or add a --next alternative that has that explicit functionality from
the start to make it less likely to rock any boats. Something like: --run

It would pause the config file reading, do the transfer with what's been given
so far and then come back and continue reading.

Then you could even have -K read from a named pipe and pipe options into that
from whereever and get curl to wait and transfer stuff as soon as it parses
the next --run from the pipe and just never quit! =)

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ:        http://curl.haxx.se/docs/faq.html
Etiquette:  http://curl.haxx.se/mail/etiquette.html