emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Karl Voit <devnull@Karl-Voit.at>
To: emacs-orgmode@gnu.org
Subject: Re: Editing HTML blocks: no special environment to edit here - solved
Date: Thu, 22 Aug 2013 19:44:55 +0200	[thread overview]
Message-ID: <2013-08-22T19-36-30@devnull.Karl-Voit.at> (raw)
In-Reply-To: 20130822163851.GE11849@kuru.dyndns-at-home.com

* Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:
> On Thu, Aug 22, 2013 at 04:46:49PM +0200, Karl Voit wrote:
>> 
>> Sorry to be cumbersome but I could not find anything related to
>> «html back-end» in the documentation. Where do I have to look in
>> order to learn how to fix my issue?
>
> All supported exporters are known as backends in Org lingo.  So I guess
> you just need a: 
>
>   (require 'ox-html)

Oh wow, it seems I missed a lot of export backends then (since 8.0).

I found [1] and [2] and added quite a number of require-statements
to my configuration :-)

Thanks for solving my issue - I am now able to edit HTML blocks!


  1. http://orgmode.org/worg/exporters/ox-overview.html
  2. http://orgmode.org/worg/org-8.0.html
-- 
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
       > get Memacs from https://github.com/novoid/Memacs <

https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github

      reply	other threads:[~2013-08-22 17:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-21  9:12 Editing HTML blocks: no special environment to edit here Karl Voit
2013-08-22  8:55 ` Karl Voit
2013-08-22  8:57   ` Nicolas Goaziou
2013-08-22 11:07     ` Karl Voit
2013-08-22 12:02       ` Nick Dokos
2013-08-22 13:03         ` Karl Voit
2013-08-22 13:59           ` Nicolas Goaziou
2013-08-22 14:46             ` Karl Voit
2013-08-22 16:38               ` Suvayu Ali
2013-08-22 17:44                 ` Karl Voit [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.orgmode.org/

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

  git send-email \
    --in-reply-to=2013-08-22T19-36-30@devnull.Karl-Voit.at \
    --to=devnull@karl-voit.at \
    --cc=emacs-orgmode@gnu.org \
    --cc=news1142@Karl-Voit.at \
    /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).