unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: numbchild@gmail.com
Cc: Org-mode <emacs-orgmode@gnu.org>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: [PROBLEM] The commit "e1f09607e0" caused org-mode inline image preview try to convert PDF file link
Date: Sat, 22 Aug 2020 15:03:13 +0200	[thread overview]
Message-ID: <87ft8eomsu.fsf@gnus.org> (raw)
In-Reply-To: <CAL1eYuK9htxPYTXi0oaKY6Vt1ePN2j4w1nOqotMKQoz4ndNWCw@mail.gmail.com> (numbchild@gmail.com's message of "Sat, 22 Aug 2020 08:12:19 +0800")

"numbchild@gmail.com" <numbchild@gmail.com> writes:

> The commit "e1f09607e0" caused this problem. I confirmed by git
> checkout a commit before it. And re-eval source code, then the problem
> is gone. This is because the commit added
> ~image-converter-file-name-extensions~ in image-convert.el library
> which includes "pdf" file extension. It uses command "gs" to convert
> pdf to image which use 100% of CPU.

I think image-converter.el should have a list of types that it shouldn't
attempt to convert, even if the backend says that it can.  PDF/PS are
obvious things -- they aren't images, but imagemagick will offer to
display them anyway.

I'll add that to Emacs 28.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2020-08-22 13:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAL1eYuLG35XwgZaGpgc_yANY_uUy2mQh=3qWL9D7E4eFcm6LSg@mail.gmail.com>
     [not found] ` <87sgclol1f.fsf@nicolasgoaziou.fr>
2020-08-22  0:12   ` [PROBLEM] The commit "e1f09607e0" caused org-mode inline image preview try to convert PDF file link numbchild
2020-08-22 13:03     ` Lars Ingebrigtsen [this message]
2020-08-22 13:29       ` [SOLVED] " numbchild
2020-08-22 13:44         ` 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=87ft8eomsu.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=numbchild@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.
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).