From: julien lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org
Subject: Re: MIME database
Date: Tue, 28 Nov 2017 11:01:54 +0100 [thread overview]
Message-ID: <1f8eda54eb31d66d64c9fdcc4138853e@lepiller.eu> (raw)
In-Reply-To: <87k1ya3gdy.fsf@gnu.org>
Le 2017-11-28 10:24, ludo@gnu.org a écrit :
> Hello,
>
> (Moving the discussions to guix-devel.)
>
> brendan.tildesley@openmailbox.org skribis:
>
>> I was wondering why my pdf documents were getting opened in Gimp by
>> default instead of Evince, so I investigated xdg-open and found it
>> uses mimeopen as a fallback, and packaged it. Turns out it didn't make
>> a difference and the issue was simply that the generated
>> mimedata.cache in xdg-mime-database had Gimp listed before Evince.
>
> Oh, good catch. Profile generation is sensitive to package order; so
> indeed, if GIMP comes first, it “wins.”
>
>> I was also I little confused that xdg-mime-database produces so many
>> conflicts with shared-mime-info. It's role appears to be to update the
>> data in shared-mime-data and have it overshadow the original data when
>> conflicts are resolved during profile generation. Looks ugly seeing
>> all those conflicts though.
>
> I guess it’s OK in that users normally don’t want to install these
> packages at all, let alone installing both in the same profile.
>
>> I had a look at Fedora's version. They just have a single
>> shared-mime-data package that runs update-mime-database, but also they
>> add a few changes to make Evince open pdf's instead of Gimp, among
>> other changes.
>>
>> This makes me feel that it's desirable for us to also tweak mimedata
>> to make it more sensible -- Pdf's should open in a pdf reader before
>> it opens in an image editor. It seems unrealistic to only tweak
>> upstream projects to make all this mimedata mesh together perfectly to
>> produce ideal default behaviour.
>
> Right, so I think the immediate course of action here would be to patch
> GIMP’s MIME data so that it does not register as a PDF viewer.
>
> If we stumble upon other issues like that, we can fix them similarly.
Thanks for investigating that.
Inkscape also wants to open pdf files ;)
>
> How does that sound?
>
> Thanks for investigating!
>
> Ludo’.
next prev parent reply other threads:[~2017-11-28 10:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171127125053.C13FF4E0018@mta-1.openmailbox.og>
2017-11-28 9:24 ` MIME database Ludovic Courtès
2017-11-28 10:01 ` julien lepiller [this message]
2017-11-28 11:23 ` Alex Vong
2017-11-28 12:57 ` Andy Wingo
2017-11-30 9:54 ` Ludovic Courtès
2017-12-01 15:05 ` Ludovic Courtès
2017-11-28 10:13 ` Andy Wingo
2017-11-29 8:19 brendan.tildesley
-- strict thread matches above, loose matches on Subject: below --
2017-11-29 9:12 brendan.tildesley
2017-11-29 11:49 brendan.tildesley
2017-11-29 11:51 brendan.tildesley
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1f8eda54eb31d66d64c9fdcc4138853e@lepiller.eu \
--to=julien@lepiller.eu \
--cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.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).