From: Tomas Nordin <tomasn@posteo.net>
To: Lars Ingebrigtsen <larsi@gnus.org>, Stefan Kangas <stefan@marxist.se>
Cc: 36771@debbugs.gnu.org
Subject: bug#36771: 27.0.50; mailcap documentation and effect missmatch
Date: Sat, 05 Oct 2019 13:09:37 +0200 [thread overview]
Message-ID: <87tv8no3da.fsf@fliptop.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87v9t5swgt.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Stefan Kangas <stefan@marxist.se> writes:
>
>> Agreed. Here I would have expected to get the more specific entry, but
>> I get the least specific entry. On my system "view" in /etc/mailcap is:
>>
>> text/*; view %s; edit=vim %s; compose=vim %s; test=test -x
>> /usr/bin/vim; needsterminal
>> text/*; view %s; edit=vi %s; compose=vi %s; needsterminal
>
> You used to get the most specific entry no matter where it was, but I
> think the change was supposed to allow ~/.mailcap to override even
> more-specific entries in /etc/mailcap.
>
> So text/* in ~/.mailcap will win over text/plain in /etc/mailcap.
>
> But I haven't looked closely at this bug report...
I could maybe summarize the report by this bald claim: The effective
logic of the `mailcap-prefer-mailcap-viewers` variable is reversed
relative its docstring.
What do you think?
Best regards
--
Tomas
next prev parent reply other threads:[~2019-10-05 11:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 7:36 bug#36771: 27.0.50; mailcap documentation and effect missmatch Tomas Nordin
2019-10-02 23:38 ` Stefan Kangas
2019-10-03 15:02 ` Lars Ingebrigtsen
2019-10-05 11:09 ` Tomas Nordin [this message]
2019-10-07 2:35 ` Lars Ingebrigtsen
2019-10-07 3:01 ` Lars Ingebrigtsen
2019-10-13 9:42 ` Tomas Nordin
2019-10-13 17:18 ` Lars Ingebrigtsen
2019-10-13 18:16 ` Tomas Nordin
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=87tv8no3da.fsf@fliptop.i-did-not-set--mail-host-address--so-tickle-me \
--to=tomasn@posteo.net \
--cc=36771@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=stefan@marxist.se \
/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/emacs.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).