[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Inline images, was Re: Variable slur thickness
From: |
David Wright |
Subject: |
Re: Inline images, was Re: Variable slur thickness |
Date: |
Wed, 16 Mar 2016 09:42:51 -0500 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Thu 10 Mar 2016 at 10:19:29 (-0600), Cynthia Karl wrote:
> On Thu, 10 Mar 2016 06:04:57 -0700 (MST) tisimst <address@hidden> schrieb:
> >
> > HTH,
> > Abraham
> >
> > P.S. Some of the power users on this list filter inline images, so if you
> > wouldn't mind making the image an attachment next time, I know they'll
> > appreciate it. :-)
>
> Why on earth would anyone filter inline images? They are extremely
> convenient. They’re right there in the email, one doesn’t have to change
> context to a browser and interrupt the flow of reading the message.
There are plenty of explanations on the web about the disadvantages of
inline images. Myself, I don't filter them, but I read emails as text,
which amounts to the same thing.
> On the other hand, for me who gets the lilypond-user messages in the Digest
> form, attachments suck big time. For example, below after the "-------- next
> part ————“ line is a link to such an attachment (I think). When I click on
> that link, the result is:
>
> > Not Found
> >
> > The requested URL
> > /archive/html/lilypond-user/attachments/20160310/4addc8f3/attachment.html
> > was not found on this server.
Agreed, there is a problem. The links are set wrongly, yet the
attachments exist elsewhere. For example, the attachment given
in the digest as
http://lists.gnu.org/archive/html/lilypond-user/attachments/20160312/6eba7c13/attachment.png
is actually at
http://lists.gnu.org/archive/html/lilypond-user/2016-03/pngHJxj6irVRF.png
> That’s not very convenient at all. Am I the only one with this problem?
> What’s the solution?
Dunno. Step one is emailing the webmaster, which I've done.
> Maybe it would be nice if inline images were also added as attachments?
Yes; maybe they will.
Cheers,
David.