From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Sharon Kimble <boudiccas@skimble.plus.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How can I get attachments to stick and actually be sent with an email using 27.0.91?
Date: Sat, 20 Jun 2020 12:53:51 -0400 [thread overview]
Message-ID: <jwv1rm9isr5.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87y2oi9cms.fsf@skimble.plus.com> (Sharon Kimble's message of "Sat, 20 Jun 2020 12:53:47 +0100")
> And searching for 'mm-substring-no-properties' in my config turns up this
[...]
> (defun mml-attach-file (file &optional type description disposition)
Well, if you silently overwrite functions like that, you get what ask
for ;-)
Stefan
prev parent reply other threads:[~2020-06-20 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 17:13 How can I get attachments to stick and actually be sent with an email using 27.0.91? Sharon Kimble
2020-06-18 17:16 ` Stefan Monnier
2020-06-18 18:00 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-06-20 11:40 ` Sharon Kimble
2020-06-20 11:53 ` Sharon Kimble
2020-06-20 16:53 ` Stefan Monnier [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
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=jwv1rm9isr5.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=boudiccas@skimble.plus.com \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).