From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Image-conversion shims
Date: Mon, 30 Sep 2019 10:06:17 +0300 [thread overview]
Message-ID: <83blv2e00m.fsf@gnu.org> (raw)
In-Reply-To: <8736gea0do.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 30 Sep 2019 06:12:03 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
> Date: Mon, 30 Sep 2019 06:12:03 +0200
>
> > Actually, why not simply add the relevant extensions to
> > auto-mode-alist, causing them to invoke image-mode?
>
> But when do we do that? To determine what the list of supported formats
> is, we have to run `image-converter--probe' (etc). But we don't know
> whether we need to do that until we know that we're going to load an
> unsupported image format. :-/
>
> I.e., we want ("*.webp" . image-mode) in auto-mode-alist, but we can't
> put it there before we've called "gm convert -list format"
I don't think I understand why we can't put the association in
auto-mode-alist before running "gm convert". Please elaborate why.
> Uhm. Perhaps map .wepb etc to a new image-mode-external that should
> just be a mode that inherits from image-mode, but would do nothing if
> the image-external-converter-mode has been toggled off?
Not "do nothing", but display an error message saying this image
format is unsupported, IMO.
next prev parent reply other threads:[~2019-09-30 7:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-28 20:06 Image-conversion shims Lars Ingebrigtsen
2019-09-28 20:37 ` Clément Pit-Claudel
2019-09-28 21:20 ` Lars Ingebrigtsen
2019-09-29 6:24 ` Eli Zaretskii
2019-09-28 21:05 ` Stefan Monnier
2019-09-28 21:21 ` Lars Ingebrigtsen
2019-09-28 23:29 ` Lars Ingebrigtsen
2019-09-29 0:01 ` Lars Ingebrigtsen
2019-09-29 7:11 ` Eli Zaretskii
2019-09-29 11:44 ` Lars Ingebrigtsen
2019-09-29 11:56 ` Eli Zaretskii
2019-09-30 4:12 ` Lars Ingebrigtsen
2019-09-30 7:06 ` Eli Zaretskii [this message]
2019-09-30 13:42 ` Lars Ingebrigtsen
2019-09-30 14:01 ` Eli Zaretskii
2019-10-01 12:06 ` Lars Ingebrigtsen
2019-10-01 12:36 ` Eli Zaretskii
2019-09-30 17:27 ` Stefan Monnier
2019-10-01 12:08 ` Lars Ingebrigtsen
2019-10-01 13:09 ` Stefan Monnier
2019-10-06 20:58 ` Juri Linkov
2019-10-07 1:41 ` Lars Ingebrigtsen
2019-10-07 18:48 ` Juri Linkov
2019-10-08 16:06 ` Lars Ingebrigtsen
2019-10-08 17:47 ` Stefan Monnier
2019-10-09 19:26 ` Lars Ingebrigtsen
2019-10-09 19:53 ` Stefan Monnier
2019-10-14 4:53 ` Lars Ingebrigtsen
2019-10-14 19:27 ` Juri Linkov
2019-10-14 19:41 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83blv2e00m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).