public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Csaba Raduly <rcsaba@gmail.com>
To: mahao_boy@sina.cn, cygwin list <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:37:00 -0000	[thread overview]
Message-ID: <CAEhDDbDGw4y0RyYs-b-2fSWwVW1WzeV34nnDkAxddhwpEojC6w@mail.gmail.com> (raw)
In-Reply-To: <20190621072718.86F8146400A4@webmail.sinamail.sina.com.cn>

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)

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2019-06-21  7:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-21  7:27 Ma Hao
2019-06-21  7:37 ` Csaba Raduly [this message]
2019-06-21  7:40 回复:Re: " Ma Hao
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=CAEhDDbDGw4y0RyYs-b-2fSWwVW1WzeV34nnDkAxddhwpEojC6w@mail.gmail.com \
    --to=rcsaba@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=mahao_boy@sina.cn \
    /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).