unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Felix E. Klee" <felix.klee@inka.de>
To: help-gnu-emacs@gnu.org
Subject: Displaying images
Date: Sun, 15 Jan 2023 11:35:41 +0100	[thread overview]
Message-ID: <87r0vwm6f6.fsf@inka.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1690 bytes --]

I am using Emacs for file management.  This involves viewing images
either in a buffer or using `image-dired`.  All worked fine for years.
However recently:

  * There a new image formats, such as AVIF, that don’t diplay out of
    the box.

  * I bought a Sony ZV-1 digital camera, and its ARW raw images don’t
    display.  I already have an idea how to solve that, not too
    important now.

Yes, those AVIF images, why don’t they display automatically?

They are supported by the latest ImageMagick and GraphicsMagick, as
tested on my up-to-date Arch Linux system.  As example, I use:

[hato.profile0.8bpc.yuv420.no-cdef.avif][1]

My Emacs config for testing is attached.  A few minutes ago, I could
open the AVIF file, and it was displayed in `fundamental-mode`.  I had
to manually do M-x `image-mode`.  Then it displayed.  Currently that
doesn’t work at all anymore.  I am greeted by: “Unknown image type”

There are two more things that are confusing me:

  * `auto-image-file-mode` by default is `nil`, but still JPEG images,
    for example, do display.  So I don’t feel like turning it on, and it
    doesn’t seem to make a difference anyhow.  Perhaps it’s a legacy
    option.

  * In the customization buffer, for “Image Converter” it says
    “graphicsmagick” and “CHANGED outside Customize.”  Note that I start
    Emacs as `emacs -q -l init.el` with the attached init
    file.  Certainly `image-converter` is not set there.

I am using: GNU Emacs 28.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.24.36, cairo version 1.17.6) of 2023-01-03

[1]: https://aomediacodec.github.io/av1-avif/testFiles/Link-U/hato.profile0.8bpc.yuv420.no-cdef.avif

[-- Attachment #2: init.el --]
[-- Type: text/plain, Size: 803 bytes --]

(setq user-init-file (or load-file-name (buffer-file-name)))
(setq user-emacs-directory (file-name-directory user-init-file))
(custom-set-variables
 ;; custom-set-variables was added by Custom.
 ;; If you edit it by hand, you could mess it up, so be careful.
 ;; Your init file should contain only one such instance.
 ;; If there is more than one, they won't work right.
 '(image-file-name-extensions
   '("png" "jpeg" "jpg" "gif" "tiff" "tif" "xbm" "xpm" "pbm" "pgm" "ppm" "pnm" "svg" "avif"))
 '(image-use-external-converter t)
 '(imagemagick-enabled-types t))
(custom-set-faces
 ;; custom-set-faces was added by Custom.
 ;; If you edit it by hand, you could mess it up, so be careful.
 ;; Your init file should contain only one such instance.
 ;; If there is more than one, they won't work right.
 )

             reply	other threads:[~2023-01-15 10:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-15 10:35 Felix E. Klee [this message]
2023-01-15 11:40 ` Displaying images Jean Louis
2023-01-15 12:09   ` Emanuel Berg
2023-01-15 19:27 ` Daniel Fleischer
2023-01-15 19:48   ` Felix E. Klee
2023-01-19  9:30 ` Felix E. Klee

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=87r0vwm6f6.fsf@inka.de \
    --to=felix.klee@inka.de \
    --cc=help-gnu-emacs@gnu.org \
    /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.
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).