From: garoth@gmail.com (Andrei Thorp)
Subject: [sup-talk] [BUG] Can't handle spaces in paths
Date: Mon, 15 Jun 2009 14:47:22 -0400 [thread overview]
Message-ID: <80055d7c0906151147h826d5beg7e5c56092149cd54@mail.gmail.com> (raw)
Hey there,
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 :)
Not much of a bug, I ln -s'd around it. Maybe something that could be
handled somehow though? I tried quotes and whitespace backslashing in
shell, but no go.
Cheers!
-AT
next reply other threads:[~2009-06-15 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 18:47 Andrei Thorp [this message]
2009-06-15 19:05 ` Guillaume Quintard
2009-06-15 19:07 ` Andrei Thorp
2009-06-15 19:18 ` William Morgan
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=80055d7c0906151147h826d5beg7e5c56092149cd54@mail.gmail.com \
--to=garoth@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