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: Sun, 13 Oct 2019 11:42:03 +0200 [thread overview]
Message-ID: <877e59asno.fsf@posteo.net> (raw)
In-Reply-To: <87lftxcl8l.fsf@gnus.org>
Hello
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> Stefan Kangas <stefan@marxist.se> writes:
>>
>>> I tried digging into this code, but found mailcap.el too confusing overall...
>>
>> Yes, it's really, really confusing.
>>
>> There's so many reversals in the way things are sorted that it's amazing
>> that it sometimes halfway works at all.
>>
>> I think I'll rewrite it some, and mark stuff explicitly where they came
>> from (user/Emacs/system), and then use that to decide what to use.
>
> I think this should perhaps now work on the trunk -- at least it works
> in my test cases. Could you test?
I don't know how to properly test some patched lisp files without
rebuilding and reinstalling. If I manually load the patched files seq.el
and mailcap.el in my "normal" emacs it works as I would expect it to
work, thanks. If I do emacs -Q and manually load those files and
(require 'mailcap)
(mailcap-mime-info "text/html")
I get
Debugger entered--Lisp error: (void-function when-let)
...
But maybe that test case is confused. What do you think?
Best regards
--
Tomas
next prev parent reply other threads:[~2019-10-13 9:42 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
2019-10-07 2:35 ` Lars Ingebrigtsen
2019-10-07 3:01 ` Lars Ingebrigtsen
2019-10-13 9:42 ` Tomas Nordin [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877e59asno.fsf@posteo.net \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.