From: daniel@wagner-home.com (Daniel Wagner)
Subject: [sup-talk] mime-view
Date: Tue, 19 Feb 2008 22:59:16 -0800 [thread overview]
Message-ID: <1203490669-sup-3520@buckwheat> (raw)
In-Reply-To: <1203442283-sup-4449@south>
Excerpts from William Morgan's message of Tue Feb 19 09:32:57 -0800 2008:
> Reformatted excerpts from Daniel Wagner's message of 2008-02-18:
> > Recently, activating attachments has stopped working.
>
> You know, in reexamining this code, I think there is a silly bug here,
> and I think it also caused the weirdness that John Bent was experiencing
> a few weeks ago.
>
> Can you try the latest (master/next) from git, or apply the following
> patch:
Applied it (by hand), still no joy. BUT! On a little more digging, it
looks like the #{} syntax wasn't properly escaping spaces in the
filename. A few \" later, I'm back in business.
system "see #{content_type}:\"#{filename}\""
Thanks,
~d
prev parent reply other threads:[~2008-02-20 6:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 4:01 Daniel Wagner
2008-02-19 17:32 ` William Morgan
2008-02-19 17:54 ` John Bent
2008-02-19 17:56 ` William Morgan
2008-02-19 18:23 ` William Morgan
2008-02-20 6:59 ` Daniel Wagner [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=1203490669-sup-3520@buckwheat \
--to=daniel@wagner-home.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