emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: "Eric Schulte" <schulte.eric@gmail.com>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: modular block exportation was patch [Feature Addition] exporting comments on org files to html
Date: Fri, 07 Nov 2008 11:02:36 -0800	[thread overview]
Message-ID: <878wrvwe9f.fsf_-_@gmail.com> (raw)
In-Reply-To: <87wsfgccv6.fsf@gmail.com> (Eric Schulte's message of "Thu, 06 Nov 2008 21:40:45 -0800")

Hi,

This has had me thinking about the exportation of blocks in general.  I
think it makes sense to pull block exportation out into it's own
component both for simplicity and for ease of code-reading, hacking, and
customization.

with a set of blocks of forms like...

#+begin_html

#+begin_src

#+begin_comment

#+begin_example

etc...

We could have an alist in which we look up the type of the block, and
call the appropriate function to handle exportation.  Users could then
add their own custom block export functions to this list.

The optional exportation of these blocks could then be controlled by a
single #+option variable which takes a list of blocks not to export.
For example

#+OPTION   hidden_blocks:comment,src

I'd be interested to hear anyone's thoughts on this.  If it sounds like
a good idea I'd be happy to take a stab at implementation.

Cheers -- Eric

next prev parent reply	other threads:[~2008-11-07 19:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-05  6:50 patch [Feature Addition] exporting comments on org files to html Eric Schulte
2008-11-06  7:05 ` Carsten Dominik
2008-11-07  5:40   ` Eric Schulte
2008-11-07 19:02     ` Eric Schulte [this message]
2008-11-10  8:26       ` modular block exportation was " Carsten Dominik
2008-11-10 15:49         ` Eric Schulte
2008-11-12  2:03         ` Eric Schulte
2008-11-12  6:50           ` Carsten Dominik

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=878wrvwe9f.fsf_-_@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=dominik@science.uva.nl \
    --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

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).