From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 963@debbugs.gnu.org
Subject: bug#963: no support for viewing bmp images?
Date: Fri, 27 Sep 2019 15:41:53 +0200 [thread overview]
Message-ID: <87ef01q2ji.fsf@gnus.org> (raw)
In-Reply-To: <CADwFkmktwFiN_D=1vHOCnxFhj3br9d3jLTcTqr5fT9PrAjvLbw@mail.gmail.com> (Stefan Kangas's message of "Fri, 27 Sep 2019 12:40:34 +0200")
Stefan Kangas <stefan@marxist.se> writes:
> I remember seeing them in stuff like tutorials for how to load an
> image in <foo> language and suchlike. Perhaps I saw was some Scheme
> stuff a couple of years ago where the examples used BMP...? I can't
> remember exactly. It might have been PNG too, to be honest.
>
> I still think it would be a nice little feature to have. But I won't
> protest if this is closed as wontfix either.
Yeah, I think this is one of those image formats we'll just have to
defer users to ImageMagick if they want to see...
This reminds me: Since we don't really want to point users towards
compiling with ImageMagick due to security concerns -- would it make
sense to write a shim over external utilities to handle exotic formats?
I mean, it would just have to call "convert" in a temp buffer to some
format we do handle (like PNG).
But I guess that doesn't really deal with the security issue, as buffer
overflows in "convert" will do pretty much the same as in Emacs. But it
would lead to fewer segfaults in Emacs itself, so perhaps it's worth
doing? It'd be a pretty trivial shim, and we could deprecate compiling
with ImageMagick for sure.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2019-09-27 13:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 22:02 bug#963: no support for viewing bmp images? xah lee
2011-07-19 20:46 ` Glenn Morris
2019-08-20 16:17 ` Stefan Kangas
2019-09-26 18:11 ` Lars Ingebrigtsen
2019-09-27 10:40 ` Stefan Kangas
2019-09-27 13:41 ` Lars Ingebrigtsen [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=87ef01q2ji.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=963@debbugs.gnu.org \
--cc=stefan@marxist.se \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.