From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: my attach this buffer
Date: Tue, 25 May 2021 09:37:04 -0700 [thread overview]
Message-ID: <87v976n51r.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87lf83grpz.fsf@mat.ucm.es>
Uwe Brauer <oub@mat.ucm.es> writes:
>> Uwe Brauer <oub@mat.ucm.es> writes:
>
>> Yes. If you want it to guess correctly you'll have to override the ".m"
>> entry in `mailcap-mime-extensions'.
>
> There is no ".m" entry!
> I just checked this variable is set by good old defvar and not
> defcustom, sigh
You're right! That must be getting picked up from my system somewhere.
You should feel free to push your own cons onto this variable, or use a
~/.mime.types file if you want to set this association for more than
just Emacs. The contents of that file will get merged with
`mailcap-mime-extensions'. I believe the file format is one line per
association, looking like:
.m text/x-foo
See the docstring and code comments of the `mailcap-parse-mimetypes'
function for a bunch of different ways to specify your mimetype
associations.
next prev parent reply other threads:[~2021-05-25 16:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 17:22 Uwe Brauer
2021-05-22 17:51 ` dick.r.chiang
2021-05-22 18:01 ` Uwe Brauer
2021-05-22 19:39 ` Eric Abrahamsen
2021-05-23 21:08 ` Uwe Brauer
2021-05-23 21:24 ` Emanuel Berg
2021-05-23 22:13 ` Emanuel Berg
2021-05-24 6:29 ` Uwe Brauer
2021-05-24 7:03 ` Emanuel Berg
2021-05-24 10:47 ` Uwe Brauer
2021-05-24 18:29 ` Eric Abrahamsen
2021-05-24 19:53 ` Uwe Brauer
2021-05-24 20:01 ` Eric Abrahamsen
2021-05-25 8:09 ` Uwe Brauer
2021-05-25 16:37 ` Eric Abrahamsen [this message]
2021-05-26 6:40 ` Uwe Brauer
2021-05-26 15:57 ` Eric Abrahamsen
2021-05-23 22:07 ` Adam Sjøgren
2021-08-23 12:06 ` Wayne Harris
2021-08-23 18:23 ` Emanuel Berg
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=87v976n51r.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).