From: David Bremner <david@tethera.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 49380@debbugs.gnu.org, notmuch@notmuchmail.org
Subject: Re: bug#49380: 27.1; is mm-inline-message supported outside Gnus?
Date: Sun, 04 Jul 2021 13:49:25 -0300 [thread overview]
Message-ID: <87im1q6n3e.fsf@tethera.net> (raw)
In-Reply-To: <878s2m15q1.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
>
> Yeah, it's confusing. `mm-inline-message' is really an "internal" Gnus
> function, while most of the other mm functions are more general.
>
> Disentangling that mess is daunting, but for that function in
> particular, I guess it wouldn't be that difficult to rewrite it to avoid
> doing anything Gnus-ish unless we're in Gnus... On the other hand, it's
> a function to display a complete message, which leaves you with a buffer
> that's pretty pointless unless you have a mail reader to interact with
> it afterwards.
I should have been more precise. I'm calling it indirectly via
mm-display-part, which is useful in the case where someone attaches a
message/rfc822 part to their message. In principle notmuch can (and in
the general case does) render the part directly, but in certain odd
fall-back cases it is handy to give a visual representation of the part
in the buffer without parsing etc.. ourselves. So the user does have a
mail reader, namely notmuch. In fact I can almost make it work by
forcing the buffer back into notmuch-show-mode after calling
mm-display-part, but that has some side-effects I'd prefer to avoid.
Thanks for thinking about my (weird?) use-cases,
David
next prev parent reply other threads:[~2021-07-04 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87sg0u6wcb.fsf@tethera.net>
2021-07-04 15:03 ` bug#49380: 27.1; is mm-inline-message supported outside Gnus? Lars Ingebrigtsen
2021-07-04 16:49 ` David Bremner [this message]
2021-07-05 13:24 ` Lars Ingebrigtsen
2021-07-06 11:37 ` David Bremner
2021-07-06 14:34 ` 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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87im1q6n3e.fsf@tethera.net \
--to=david@tethera.net \
--cc=49380@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).