From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [BUG] Can't handle spaces in paths
Date: Mon, 15 Jun 2009 12:18:28 -0700 [thread overview]
Message-ID: <1245093476-sup-4708@entry> (raw)
In-Reply-To: <80055d7c0906151147h826d5beg7e5c56092149cd54@mail.gmail.com>
Reformatted excerpts from Andrei Thorp's message of 2009-06-15:
> I just downloaded a whole lot of mail from my gmail account via
> offlineimap, and tried to add a source with a space. In short, sup
> doesn't like this. It tries to do a split somewhere and it doesn't
> work out for it so well :)
Try putting a %20 instead of a space. A sad consequence of using URIs to
specify sources.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2009-06-15 19:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 18:47 Andrei Thorp
2009-06-15 19:05 ` Guillaume Quintard
2009-06-15 19:07 ` Andrei Thorp
2009-06-15 19:18 ` William Morgan [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=1245093476-sup-4708@entry \
--to=wmorgan-sup@masanjin.net \
/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