Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: Printing the URL in the error messages when --fail is passed?
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Paul Gilmartin via curl-users <curl-users_at_lists.haxx.se>
Date: Sun, 24 Jul 2022 11:44:13 -0600
On 7/24/22 10:07:44, Timothe Litt via curl-users wrote:
> ...
> But the current behavior is analogous to
>
> cp z* x* foo/
>
> returning 'file not found' instead of "cp: cannot stat 'x*': No such
> file or directory".
>
Would it be better to send such messages to stderr, as "cp" does,
rather than to stdout?
Optionally? (-w=/dev/fd/2?)
What if the OS has no "stderr"? (I know one that hasn't.)
Date: Sun, 24 Jul 2022 11:44:13 -0600
On 7/24/22 10:07:44, Timothe Litt via curl-users wrote:
> ...
> But the current behavior is analogous to
>
> cp z* x* foo/
>
> returning 'file not found' instead of "cp: cannot stat 'x*': No such
> file or directory".
>
Would it be better to send such messages to stderr, as "cp" does,
rather than to stdout?
Optionally? (-w=/dev/fd/2?)
What if the OS has no "stderr"? (I know one that hasn't.)
-- gil -- Unsubscribe: https://lists.haxx.se/listinfo/curl-users Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2022-07-24