public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: wget-1.15-1 vx wget-1.13-4, LANG and cron
Date: Tue, 13 May 2014 22:51:00 -0000	[thread overview]
Message-ID: <5372A150.3060304@redhat.com> (raw)
In-Reply-To: <CAAfYxYHFYq1ys2yV6LRsarp4T5=Dvfn2cRwLFif5NvoWkMZcQg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]

On 05/13/2014 03:49 PM, First Last wrote:
> I had trouble when I updated to wget-1.15-1.
> 
> I have a cron script that grabs a camera picture using
> wget.  It failed with the new wget-1.15-1.
> 
> 1) wget stderr has a line:
>      Saving to: 'filename'
> 
> In wget-1.13.4-1 the delimiter before the filename is a
> backtick and after the filename there is a single quote.

Yes, this was an intentional change upstream (many GNU projects have
been ditching `' quoting in favor of '' quoting, ever since GNU Coding
Standards were changed in light of modern typography looking ugly
compared to the way it looked 30 years ago when GNU first championed `').

> Also if the URL contains a <space> the filename has
> a <space>.
> 
> In wget-1.15-1 both delimiters are single quotes, at
> least with LANG=C.  A space in the URL results in
> a "%20" in the filename.

Nothing here is cygwin-specific, as I just built wget from stock
upstream.  You'll get better response if you take your issues upstream,
since I suspect they are reproducible on Linux.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

      reply	other threads:[~2014-05-13 22:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 22:48 First Last
2014-05-13 22:51 ` Eric Blake [this message]

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=5372A150.3060304@redhat.com \
    --to=eblake@redhat.com \
    --cc=cygwin@cygwin.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).