[-- Attachment #1: Type: text/plain, Size: 542 bytes --] 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. Maybe I am using the wrong construct and should be using something other than a drawer? Thanks! -Tom -- Thomas Moyer tommoyer@gmail.com [-- Attachment #2: Type: text/html, Size: 726 bytes --]
Hi Thomas,
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.
Best,
--
Bastien
Hello,
Bastien <bzg@altern.org> 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.
Regards,
--
Nicolas Goaziou
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 #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 --]
Hi Thomas,
Thomas Moyer wrote:
> So what would I need to do to use the "new exporter"?
--8<---------------cut here---------------start------------->8---
(require 'org-export)
(require 'org-e-ascii) ; if you want
(require 'org-e-html) ; if you want
;; LaTeX back-end for Org generic export engine
(require 'org-e-latex)
(require 'org-e-beamer)
;; bind the new exporter dispatch to a key sequence
(define-key org-mode-map (kbd "C-c E") 'org-export-dispatch)
--8<---------------cut here---------------end--------------->8---
and then use `C-c E' instead of `C-c C-e'.
Best regards,
Seb
--
Sebastien Vauban
Sebastien Vauban <wxhgmqzgwmuf@spammotel.com> wrote: > Hi Thomas, > > Thomas Moyer wrote: > > So what would I need to do to use the "new exporter"? > > (require 'org-export) > IIUC, this is not needed any longer: each specific exporter below does a require on it. Nick > (require 'org-e-ascii) ; if you want > > (require 'org-e-html) ; if you want > > ;; LaTeX back-end for Org generic export engine > (require 'org-e-latex) > > (require 'org-e-beamer) > > ;; bind the new exporter dispatch to a key sequence > (define-key org-mode-map (kbd "C-c E") 'org-export-dispatch) > > and then use `C-c E' instead of `C-c C-e'. > > Best regards, > Seb > > -- > Sebastien Vauban > >