Hi Carsten,
You can find the commit in the special-blocks branch of my github
repository. I've tested exporting both LaTeX and HTML.
Cheers,
Chris
Carsten Dominik wrote:
On May 4, 2009, at 9:52 AM, Chris Gray wrote:
Hi Carsten,
That seems like a good solution. I will work on it and
Hi Carsten,
That seems like a good solution. I will work on it and test it over the
next couple of days and let you know when it is ready. Do you have any
preference for the name of the file?
BTW, I also have signed and sent the copyright papers. I don't know if
that's necessary for a contrib
On May 4, 2009, at 9:52 AM, Chris Gray wrote:
Hi Carsten,
That seems like a good solution. I will work on it and test it over
the
next couple of days and let you know when it is ready. Do you have
any
preference for the name of the file?
Hard to find a good name
org-block2env.el
Hi Chris,
I have been pondering about this idea, and I prefer to not integrate
it into the Org core because I think it may lead to undesired behavior,
in particular in the other backends like docbook or ASCII.
However, I have just created three new hooks
* org-exp.el
Hi Chris,
Normally a request for a patch shuts people up, not in your case. :-)
Very interesting, I like how you did this parallel to the
other, similar environments that also require internal
processing.
I am quite over committed right now and have a trip coming up,
and I will need to think
Hi Carsten,
I took up your challenge and made a patch that does what I want. It
does what I suggested in my previous email in that it allows one to
put #+begin_foo and #+end_foo tags in the body of an org file. These
tags allow you to change the environment of the text between them.
What that
Hi Chris,
no, this is really by design the way it is. Org-mode has its own
markup. As a bonus to people used to LaTeX, it allows certain
LaTeX constructs to be intermingled into the file. For LaTeX
export, it will export these *literally*, the entire construct.
For HTML export, you can
