On 2025-10-04 10:57:42, Ralph Ronnquist via Dng wrote:
> On Fri, Oct 03, 2025 at 10:58:47AM -0400, Walter Dnes wrote:
> > On Fri, Oct 03, 2025 at 11:17:42AM +0100, fraser via Dng wrote
> > >
> > > chrome://settings/content/pdfDocuments
> > >
> > > change to 'download'
> >
> > Thank you. That's "the lesser of two evils". What I'd like in a
> > perfect world is to pass PDFs to "mupdf" automatically, i.e.
> >
> > mupdf -I pdf-filenmae
> >
> > The "-I" inverts display. Instead of black font on a garish white
> > background, I get white font on a dark background. I that possible?
>
> It used to be possible to update /etc/mailcap for declaring the
> handling of various document types. Unfortunately this seems to have
> grown into a "forest" of competing ways of overriding, but possibly
> you can get away with:
> (as root) adding your handler in a file into /usr/lib/mime/packages/
> and then (as root) removing /usr/share/applications/mimeinfo.cache
> and then (as root) run update-mime
> ans then restart your chrome browser

I'm having a similar problem, with GIMP installed, GIMP gets to open
PDFs, it's not very good at that. Without GIMP my web browser opens
them, it's a little better. What I actually want is one of the actual
PDF readers I have installed to be used. mupdf, qpdfview, anything else
that'll open them no matter how I open them.

None of the above stuff helped.

So, what's the next tree in this forest? If it falls, does it sound like
one hand clapping?

--
A big old stinking pile of genius that no one wants
coz there are too many silver coated monkeys in the world.