emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Peter Davis <pfd@pfdstudio.com>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-mime-org-buffer-htmlize can't find back-end
Date: Thu, 07 Apr 2016 07:22:56 -0400	[thread overview]
Message-ID: <m2wpo9mzn3.fsf@PFDStudio-Air.home> (raw)
In-Reply-To: <87y48phlez.fsf@gmx.us> (rasmus@gmx.us's message of "Thu, 07 Apr 2016 10:29:08 +0200")


Rasmus <rasmus@gmx.us> writes:

> Hi Peter,
>
> Peter Davis <pfd@pfdstudio.com> writes:
>
>> I used to be able to use org-buffer-org-mime-htmlize to send my org
>> documents as multipart/alternative html & text email. For some
>> reason, this is stopped working, and now displays
>>
>> Unknown "nil" back-end: Aborting export
>>
>> In the *Messages* buffer, I see
>>
>> org-export-barf-if-invalid-backend: Unknown "nil" back-end: Aborting export
>>
>> So how is the back-end supposed to be defined? (And why might it have
>> broken?) I haven't not made any related changes in a *long*
>> time.
>
> Could you provide a reproducible example starting with emacs -q?
>
> I can't reproduce it here by
>
> 1. starting from emacs -q with latest org from master
> 2. creating an org buffer with the content:
>    - 1
>    - 2
> 3. calling org-mime-org-buffer-htmlize on this buffer.

Thank you, Rasmus, but ...

If I start emacs with -q, it doesn't know about org. It can't set org-mode, or run org-mime commands. Is there a way to load this
manually?

Also, can "the latest org from master" be gotten through package manager?

Thanks!
-pd

  reply	other threads:[~2016-04-07 11:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-06 15:29 org-mime-org-buffer-htmlize can't find back-end Peter Davis
2016-04-07  8:29 ` Rasmus
2016-04-07 11:22   ` Peter Davis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-04-07 12:32 Peter Davis
2016-04-07 12:41 Peter Davis
2016-04-07 21:23 ` Rasmus
2016-04-07 22:38   ` Peter Davis

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=m2wpo9mzn3.fsf@PFDStudio-Air.home \
    --to=pfd@pfdstudio.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \
    /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).