From: "Ma Hao" <mahao_boy@sina.cn>
To: "Csaba Raduly" <rcsaba@gmail.com>, "cygwin" <cygwin@cygwin.com>
Subject: 回复:Re: Running 'curl' with '-o' option failed with error "curl: (23) Failed writing body (0 != 720)"
Date: Fri, 21 Jun 2019 07:40:00 -0000 [thread overview]
Message-ID: <20190621074049.8D3DF4140097@webmail.sinamail.sina.com.cn> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=GBK, Size: 1709 bytes --]
Thanks for pointing that out.Appreciate your quick responding.
--------------------------------
Ma HaoBR
email: mahao_boy@sina.cn
Phone: +86(0)13981759428
Location: Tianfu Software Park, Tianfu avenue, High Tech Zone, Chengdu, Sichuan Province, China
----- ÔʼÓʼþ -----
·¢¼þÈË£ºCsaba Raduly <rcsaba@gmail.com>
ÊÕ¼þÈË£ºmahao_boy@sina.cn, cygwin list <cygwin@cygwin.com>
Ö÷Ì⣺Re: Running 'curl' with '-o' option failed with error "curl: (23) Failed writing body (0 != 720)"
ÈÕÆÚ£º2019Äê06ÔÂ21ÈÕ 15µã37·Ö
Hi,
On Fri, Jun 21, 2019 at 9:28 AM Ma Hao <mahao_boy@sina.cn> wrote:
>
> Hi,
> I was running into the problem when I tried to download spring:
> $ curl https://codeload.github.com/spring-projects/spring-framework/zip/master -o /home/cdmahao/
You told curl to write the download to a file named /home/cdmahao/
Unfortunately, there is already a directory named /home/cdmahao/, and
curl can't write a file to a directory.
You need to give the name of a file to -o
$ curl https://codeload.github.com/spring-projects/spring-framework/zip/master
-o /home/cdmahao/master.zip
curl works differently from wget. wget invents a filename based on the
URL. curl does not do that.
Csaba
--
You can get very substantial performance improvements
by not doing the right thing. - Scott Meyers, An Effective C++11/14 Sampler
So if you're looking for a completely portable, 100% standards-conformat way
to get the wrong information: this is what you want. - Scott Meyers (C++TDaWYK)
\x03BKCB\x1cØ\x19[H\x1c\^[Ü\x1cÎ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÜ\x1cØ\x19[\Ë\x1d^[[\x03BTN\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÙ\KÃB^[ØÝ[Y[\x18]\x1a[Û\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÙ^[ØÜË\x1d^[[\x03B[ÝXØÜXH\x1a[Î\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÛ[\vÈÝ[ÝXØÜXK\Ú[\^[\x19CBB
next reply other threads:[~2019-06-21 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 7:40 Ma Hao [this message]
2019-06-21 20:36 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190621074049.8D3DF4140097@webmail.sinamail.sina.com.cn \
--to=mahao_boy@sina.cn \
--cc=cygwin@cygwin.com \
--cc=rcsaba@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).