unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 33587@debbugs.gnu.org
Subject: bug#33587: [PROPOSED] Default to disabling ImageMagick
Date: Mon, 03 Dec 2018 14:08:29 -0500	[thread overview]
Message-ID: <4qo9a2xwb6.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <20181202180919.32270-1-eggert@cs.ucla.edu> (Paul Eggert's message of "Sun, 2 Dec 2018 10:09:19 -0800")


I'm a bit surprised by the lack of objections so far, though it's early
days yet of course. Maybe it's an experiment that needs to be tried out
for the implications to be seen.

A related alternative would be to lower the priority of the ImageMagick
backend. At the moment, visiting eg a png image uses ImageMagick rather
than libpng if both are linked in.





  parent reply	other threads:[~2018-12-03 19:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-02 18:09 bug#33587: [PROPOSED] Default to disabling ImageMagick Paul Eggert
2018-12-02 18:15 ` Eli Zaretskii
2018-12-02 19:13 ` Andreas Schwab
2018-12-02 23:51   ` Paul Eggert
2018-12-03 21:09     ` Alan Third
2018-12-03 19:08 ` Glenn Morris [this message]
2018-12-03 19:35   ` Paul Eggert
2018-12-03 19:40     ` Glenn Morris
2018-12-04 16:51   ` David Engster
2018-12-04 17:00     ` Glenn Morris
2018-12-04 17:38       ` David Engster
2018-12-04 18:16       ` Glenn Morris
2018-12-10 17:49 ` Paul Eggert
     [not found] <8336qb3upt.fsf@gnu.org>
     [not found] ` <20190102211241.GA53734@breton.holly.idiocy.org>
     [not found]   ` <837efk335e.fsf@gnu.org>
     [not found]     ` <20190104190914.GA61852@breton.holly.idiocy.org>
     [not found]       ` <8336q82myq.fsf@gnu.org>
     [not found]         ` <20190104224558.GA63257@breton.holly.idiocy.org>
     [not found]           ` <20190110194250.GA22478@breton.holly.idiocy.org>
     [not found]             ` <cda98d78-268c-2464-36d3-cc03a4db97ef@cs.ucla.edu>
2019-05-14  6:15               ` Paul Eggert

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=4qo9a2xwb6.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=33587@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    /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).