From: Peter Davis <pfd@pfdstudio.com>
To: emacs-orgmode@gnu.org
Subject: Re: Can't email multipart/alternative anymore
Date: Fri, 23 Oct 2015 16:57:44 -0400 [thread overview]
Message-ID: <562A9F48.7020203@pfdstudio.com> (raw)
In-Reply-To: <877fmdz567.fsf@nicolasgoaziou.fr>
On 10/23/15 4:44 PM, Nicolas Goaziou wrote:
> Hello,
>
> Aaron Ecay <aaronecay@gmail.com> writes:
>
>> Based on the backtrace, I think that if you do M-x load-library RET
>> ox-org RET your error should disappear.
>>
>> If that’s the cause, the attached (draft) patch should give a better
>> error message in cases like this.
> Thank you.
>
> However, `org-export-barf-if-invalid-backend' raises an error, not
> a user-error. IOW, it doesn't need to be verbose: it is a bug if a user
> sees it anyway.
Actually, I didn't see the barf part in the mini-buffer. All I saw there
was:
Unknown "nil" back-end: Aborting export
I copied the rest from *Messages*
> I suggest to (require 'ox-org) where appropriate and fix the issue.
> I didn't look closely at the problem so you know better than me where
> this line should be added.
I replied earlier, but it doesn't seem to have shown up on the list yet.
Explicitly loading ox-org *did* fix the problem for me, but I already have
(require 'ox-org)
in my .emacs file, so I'm not sure why that was ineffective.
Thanks.
-pd
next prev parent reply other threads:[~2015-10-23 20:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 12:05 Can't email multipart/alternative anymore Peter Davis
2015-10-23 13:05 ` Aaron Ecay
2015-10-23 20:44 ` Nicolas Goaziou
2015-10-23 20:57 ` Peter Davis [this message]
2015-10-24 12:07 ` Nicolas Goaziou
2015-10-24 13:28 ` Peter Davis
2015-10-24 14:28 ` Nicolas Goaziou
2015-10-28 14:11 ` Peter Davis
2015-10-27 15:15 ` Aaron Ecay
-- strict thread matches above, loose matches on Subject: below --
2015-10-28 15:23 Peter Davis
2015-10-23 13:22 Peter Davis
2015-10-23 11:55 Peter Davis
2015-10-22 19:19 Peter Davis
2015-10-22 21:19 ` Rasmus
2015-10-22 21:20 ` Nick Dokos
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=562A9F48.7020203@pfdstudio.com \
--to=pfd@pfdstudio.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.