emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thomas Moyer <tommoyer@gmail.com>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org, Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: Question about HTML export, drawers, and links
Date: Fri, 12 Oct 2012 21:22:22 -0400	[thread overview]
Message-ID: <CAJMnJ1XSwG1kfSrjtgZOU66PpzRtGLai9cP+N_oXKB0kx91Khw@mail.gmail.com> (raw)
In-Reply-To: <877grn4a9r.fsf@bzg.ath.cx>

[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]

So what would I need to do to use the "new exporter"?

-Tom

--
Thomas Moyer
tommoyer@gmail.com



On Fri, Sep 21, 2012 at 12:21 PM, Bastien <bzg@altern.org> wrote:

> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>
> >> Thomas Moyer <tommoyer@gmail.com> writes:
> >>
> >>> I have a set of files that I put notes in that I would like to export
> >>> to HTML. When I do this, I have configured everything to allow
> >>> certain drawers to included in the export, but those drawers are put
> >>> in <pre> blocks. Is there a way to convince the export mechanism to
> >>> treat links inside drawers as links that need exported. I put a link
> >>> in the drawer to another file and would like the link to work.
> >>
> >> This is not currently possible.
> >>
> >> The new HTML exporter (contrib/lisp/org-e-html.el) supports using a
> >> custom function to export drawers.  It is not easily usable for now,
> >> but maybe you can explore from there.
> >
> > AFAIU, the new exporter defaults to what the OP is asking for.
>
> Indeed, thanks for double-checking.
>
> --
>  Bastien
>

[-- Attachment #2: Type: text/html, Size: 1832 bytes --]

  reply	other threads:[~2012-10-13  1:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12 18:25 Question about HTML export, drawers, and links Thomas Moyer
2012-09-19 10:57 ` Bastien
2012-09-19 12:56   ` Nicolas Goaziou
2012-09-21 16:21     ` Bastien
2012-10-13  1:22       ` Thomas Moyer [this message]
2012-10-13  7:49         ` Sebastien Vauban
2012-10-13 13:26           ` 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

  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=CAJMnJ1XSwG1kfSrjtgZOU66PpzRtGLai9cP+N_oXKB0kx91Khw@mail.gmail.com \
    --to=tommoyer@gmail.com \
    --cc=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    /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).