From: Sharon Kimble <boudiccas@skimble.plus.com>
To: ding@gnus.org
Subject: Re: How to save inline photos?
Date: Sun, 12 Dec 2021 15:51:03 +0000 [thread overview]
Message-ID: <87wnk93jq0.fsf@skimble.plus.com> (raw)
In-Reply-To: <87mtl85w4k.fsf@tullinup.koldfront.dk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Adam Sjøgren <asjo@koldfront.dk> writes:
> Russ writes:
>
>> You can also use K b to show buttons for all the MIME parts and then use
>> K o to save specific MIME parts. (K b is helpful first so that you know
>> what number the MIME part you want to save has.)
>
> Nice!
>
> I think I have buttons turned on by default, so I don't have to go "K b".
>
> Ahh, yes, I have this in my ~/.gnus:
>
> (add-to-list 'gnus-buttonized-mime-types "image/.*")
>
>
> ,----[ C-h v gnus-buttonized-mime-types RET ]
> | gnus-buttonized-mime-types is a variable defined in ‘gnus-art.el’.
> |
> | Its value is
> | ("multipart/encrypted" "multipart/signed" "image/.*" "message/feedback-report" "application/gzip" "application/tlsrpt\\+gzip" "application/zip")
> | Original value was nil
> |
> | List of MIME types that should be given buttons when rendered inline.
> | If set, this variable overrides ‘gnus-unbuttonized-mime-types’.
> | To see e.g. security buttons you could set this to
> | ‘("multipart/signed")’. You could also add "multipart/alternative" to
> | this list to display radio buttons that allow you to choose one of two
> | media types those mails include. See also ‘mm-discouraged-alternatives’.
> | This variable is only used when ‘gnus-inhibit-mime-unbuttonizing’ is nil.
> |
> | This variable was introduced, or its default value was changed, in
> | version 22.1 of Emacs.
> | You can customize this variable.
> |
> `----
>
> Sometimes it's a little dangerous with these customizations, you tend to
> forget :-)
>
Thanks Adam and Russ for your comments and suggestions, but I've not
tried them as my relative sent me the photos as attachments, so I was
able to download them with no problems. I have though Adam included your
code snippet into my config for any future photos.
Thanks
Sharon.
- --
Debian 11, fluxbox 1.3.7, emacs 28.0.50, org 9.5.1
-----BEGIN PGP SIGNATURE-----
iQJPBAEBCgA5FiEELSc/6QwVBIYugJDbNoGAGQr4g1sFAmG2GmcbHGJvdWRpY2Nh
c0Bza2ltYmxlLnBsdXMuY29tAAoJEDaBgBkK+INbTgAP/3z58E7J2JirgUMb5zcA
s/UJ3iFXUkny+FOV/8FctCo7FVKBE3tpLnE32E62gPLqe0LLgq2eJgtcmw+SHE29
qX591enYSJG3SY8ClfPET5K9ulxI4PxXJxSFITKErWpV1QxLpsBiPiIwOq0Ko78G
tJ90xDthkXXTHCmS6U2skaBfnL56fAsQfcCJawhFH1EdHwp4Rw6uZFnni8GDgi1b
6gmyCoMPBRP3ouvRnTlcXDAbJpH1I6JDUHsKmnlYAJ/N5MLe4oaxAQgZvOp5LA6u
UYbPjbLgOigUNgMttk6qIgUbu00OsHXq/kUhMQbXiPnVhwI13FO5jphQ7qgMzBvV
px/CYaLSlPTkpIKlS0/zJMGezZJIKe9ekJGQIqVWLH+7C9O2bXlnWSuvsS2an83T
pOED3mq6Rh2kloqYKyGkFpb+z73HRfVO0OdxwKQx1nECOLDpHQNKmA+guTEYL3In
9MJOKg5a5OFrmU9TXLu7iqvO6vs/ePRzqPFi+kO/QxL6LXmHUThDKiClG1KqZ/uR
fLuuMvQCDSvfrq36HASII7eQbyRLUxW6wsgS+dlndFHK6qof1pTs+7PXnkrDXcC/
Evp20LzEwQ7eRX1eJTCn/g/5K8cAUH8IiMQIyVPqwTWPSxw/KqNUi7+3v8HzqRAv
jOR3mpSIyR4omMPWDL4zckAv
=hIh4
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2021-12-12 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 18:30 Sharon Kimble
2021-12-09 19:36 ` Adam Sjøgren
2021-12-10 0:56 ` Russ Allbery
2021-12-10 4:44 ` Byung-Hee HWANG
2021-12-10 15:15 ` Adam Sjøgren
2021-12-12 15:51 ` Sharon Kimble [this message]
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=87wnk93jq0.fsf@skimble.plus.com \
--to=boudiccas@skimble.plus.com \
--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).