On 12/8/23 16:53, David wrote:
On Fri, 8 Dec 2023 at 21:45, Paul M Foster <pa...@quillandmouse.com> wrote:
On Fri, Dec 08, 2023 at 11:04:54AM -0600, David Wright wrote:
On Fri 08 Dec 2023 at 11:56:12 (-0500), Paul M Foster wrote:
I'm on Debian bookworm, using neomutt for email. Where there is an image to
view, viewing it in neomutt calls up one of the ImageMagick programs. I've set
the mailcap_path variable in my neomutt config to point to ~/.mailcap, and
set an entry in there for image/jpg to point to /usr/bin/feh. I've even set
↑↑↑ try jpeg
the "display" alternative to feh with update-alternatives. Still, mutt is
calling an imagemagick program to display jpgs.
First, if alternatives doesn't point to the imagemagick program, and the
mailcap file doesn't point to it, and there's nothing in the neomutt config
pointing to the imagemagick program, then where the heck is it getting that
as the program to use to display images?
Second, how do I fix this so that mutt uses feh to display images?
I can't believe that worked. The /etc/mailcap has both (jpg and jpeg), and
the files I was looking at had a "jpg" extension.
Hi, the filename extension is usually irrelevant on Linux, because
Linux tools typically
use the standard 'file' command to inspect the content of the
fileinstead of relying on
the filename to indicate content.
In Unix and Linux there isn't a file extension, that is a microsoft
invention.
Unix and Linux filespecs are just a bunch of characters
https://www.linfo.org/file_name.html
The period in a linux filespec is just a period and nothing more
What is more likely important is that the keywords in the output of
'file <imagefile>'
command are correctly specified in your desired configuration.
--
It's not easy to be me
