From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Juan José García Ripoll" <juanjose.garcia.ripoll@csic.es>
Cc: 40247@debbugs.gnu.org
Subject: bug#40247: 27.0.90; mailcap-mime-data erased when parsing mime parts
Date: Sun, 02 Aug 2020 08:20:23 +0200 [thread overview]
Message-ID: <87tuxlmuvs.fsf@gnus.org> (raw)
In-Reply-To: <86eete20ef.fsf@csic.es> ("Juan José García Ripoll"'s message of "Thu, 26 Mar 2020 23:53:44 +0100")
Juan José García Ripoll <juanjose.garcia.ripoll@csic.es> writes:
> Symptoms:
> - Start Emacs in a system without ~/.mailcap
> - Launch Gnus
> - Open an email / news that has some part in text/html
> - mailcap-mime-data is erased and none of the default viewers are
> available any more.
>
> The problem persits if Emacs is customized using mailcap-add
Oops. This is all such a mess -- we have defaults coming from Emacs via
mailcap-mime-data, system defaults from /etc and user defaults from
~/.mailcap and mailcap-add...
The problem is that we don't keep track of where and how things are
added -- it's all just stored in mailcap-mime-data, and reconstructing
the precedence (for instance, when the user edits ~/.mailcap) is
impossible.
The fix I made in October is clearly wrong, but it basically works for
the basic (and common) "respect my ~/.mailcap" file case.
But I'm not quite sure how to go about fixing this bug... Hm. I think
perhaps we have to stop messing about with the mailcap-mime-data
variable when we compute the precedence. So mailcap-parse-mailcaps
should heed all the files, and mailcap-mime-info, but store the computed
data in a new variable, that will then be consulted when trying to
determine what viewers to use.
I'll take a whack at implementing it that way and then see how that goes.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-08-02 6:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 22:53 bug#40247: 27.0.90; mailcap-mime-data erased when parsing mime parts Juan José García Ripoll
2020-06-28 17:11 ` Basil L. Contovounesios
2020-06-28 17:20 ` Eli Zaretskii
2020-06-28 17:45 ` Basil L. Contovounesios
2020-06-28 18:19 ` Eli Zaretskii
2020-08-02 6:20 ` Lars Ingebrigtsen [this message]
2020-08-02 7:05 ` Lars Ingebrigtsen
2020-08-03 14:41 ` Juan José García-Ripoll
2020-08-04 8:35 ` Lars Ingebrigtsen
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=87tuxlmuvs.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=40247@debbugs.gnu.org \
--cc=juanjose.garcia.ripoll@csic.es \
/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).