emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: Questions about mail, MIME, etc.
Date: Fri, 09 May 2014 09:45:52 +0800	[thread overview]
Message-ID: <87vbtf67xr.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 20140508164359.GB88364@pdavismbp15.iscinternal.com

Peter Davis <pfd@pfdstudio.com> writes:

> On Thu, May 08, 2014 at 10:34:26PM +0800, Eric Abrahamsen wrote:
>> Peter Davis <pfd@pfdstudio.com> writes:
>> 
>> Yeah I got that error too, a while ago, and your message prompted me to
>> look at it. It seems like org-mime is just a bit behind the state of
>> org-export, and fixing that one dead function link is enough to make it
>> work again. I've attached a patch.
>
> Excellent! That worked. Thank you!

Okay, I'll start a new thread and see if we can get the patch accepted.

>> 
>> Generating a message buffer is pretty much hard-coded into org-mime.
>> Once you're in that buffer, though, the (non-interactive) function
>> mml-generate-mime will return the fully encoded mime message as a
>> string -- you could save that to a file and do something else with it.
>> I'm not 100% confident that's the simplest way to do that.
>
> Ok, I was able to send the message through gnus, even though I don't (normally) use it as a mail reader.
>
>> >  3) What I'd really like is a multipart/alternative message where
>> > one part is text/plain, and looks exactly like the emacs buffer
>> > display, and the other part is text/html, and
>> >     looks like what org would export to html, complete with tables, images, etc.
>> 
>> As far as I know, that's exactly what org-mime does!
>
> Almost. It looks like org-mime puts the actual contents of the buffer
> into the text/plain part, including links, etc. that would normally be
> hidden on display. I think it would be
> more useful to make the text/plain part contain what would be output from exporting to text. But maybe that's just my preference.

org-mime assumes a native 'org export format for the plain text part of
the email. That looks like it's hard-coded in `org-mime-compose',
unfortunately.

Eric

  reply	other threads:[~2014-05-09  1:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 13:31 Questions about mail, MIME, etc Peter Davis
2014-05-08 14:34 ` Eric Abrahamsen
2014-05-08 15:31   ` Peter Davis
2014-05-08 16:44   ` Peter Davis
2014-05-09  1:45     ` Eric Abrahamsen [this message]
2014-05-10 23:46 ` Peter Davis
2014-05-11  3:05   ` Eric Abrahamsen
2014-05-11 17:35     ` Peter Davis
2014-05-12  1:37       ` Eric Abrahamsen

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vbtf67xr.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=emacs-orgmode@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.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).