From: Alex Vong <alexvong1995@gmail.com>
To: julien lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org
Subject: Re: MIME database
Date: Tue, 28 Nov 2017 19:23:30 +0800 [thread overview]
Message-ID: <87y3mqir4d.fsf@gmail.com> (raw)
In-Reply-To: <1f8eda54eb31d66d64c9fdcc4138853e@lepiller.eu> (julien lepiller's message of "Tue, 28 Nov 2017 11:01:54 +0100")
[-- Attachment #1: Type: text/plain, Size: 2296 bytes --]
julien lepiller <julien@lepiller.eu> writes:
> 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 ;)
>
On my laptop, the recommended programs include evince, libreoffice draw,
gimp, inkscape, imagemagick and winebrowser. I am not running guixsd
though.
>>
>> How does that sound?
>>
>> Thanks for investigating!
>>
>> Ludo’.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-11-28 11:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 12:50 [bug#29472] [patch 0/4] Add perl-file-mimeinfo and dependencies; add it as an input to xdg-utils brendan.tildesley
2017-11-27 12:54 ` [bug#29472] [PATCH 1/4] gnu: Add perl-file-basedir Brendan Tildesley
2017-11-27 12:54 ` [bug#29472] [PATCH 2/4] gnu: Add perl-file-desktopentry Brendan Tildesley
2017-11-27 12:54 ` [bug#29472] [PATCH 3/4] gnu: Add perl-file-mimeinfo Brendan Tildesley
2017-11-27 12:54 ` [bug#29472] [PATCH 4/4] gnu: xdg-utils: Add perl-file-mimeinfo as an input Brendan Tildesley
2017-11-28 9:44 ` bug#29472: [PATCH 1/4] gnu: Add perl-file-basedir Ludovic Courtès
2017-11-28 9:24 ` MIME database Ludovic Courtès
2017-11-28 10:01 ` julien lepiller
2017-11-28 11:23 ` Alex Vong [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2017-11-29 8:19 brendan.tildesley
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y3mqir4d.fsf@gmail.com \
--to=alexvong1995@gmail.com \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.