From: Carsten Dominik <carsten.dominik@gmail.com>
To: Chris Gray <chrismgray@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: markup in environments in latex export
Date: Mon, 4 May 2009 16:28:36 +0200 [thread overview]
Message-ID: <C1719B25-961D-4C20-B543-8C5D66E699F1@gmail.com> (raw)
In-Reply-To: <867i0xs3s4.fsf@portan.ibr.cs.tu-bs.de>
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
org-anyblock.el
I don't know, your call.
>
> BTW, I also have signed and sent the copyright papers. I don't know
> if
> that's necessary for a contrib package, but now it's done...
It is not necessary for a contrib package, but it will be good to have
anyway. Maybe this add-on will move into the core distro eventually
(turned off by default), or maybe you will contribute other patches.
Thanks.
- Carsten
>
> Cheers,
> Chris
>
> Carsten Dominik wrote:
>
>> 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 (org-export-preprocess-after-blockquote-hook): New
>> hook.
>> (org-export-preprocess-string): Run the new hook.
>
>> * org-latex.el (org-export-latex-after-blockquotes-hook): New
>> hook.
>> (org-export-latex-preprocess): Run the new hook.
>
>> * org-html.el (org-export-html-after-blockquotes-hook): New hook.
>> (org-export-as-html): Run the new hook.
>
>> which would allow to easily implement your idea as an add-on package
>> that we could include in the contrib directory. Would you like to
>> reformulate your patch into a small add-on? The only thing I would
>> like to ask is to keep it LaTeX/HTML-specific, and this means that
>> the action to turn #+begin_..... into the cookies should be wrapped
>> into
>
>> (when (or latexp htmlp)
>> .......
>> )
>
>
>
>> latexp and htmlp are a local variables available when the
>> first of the three hooks is run.
>
>> - Carsten
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2009-05-04 14:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 8:49 markup in environments in latex export Chris Gray
2009-04-16 12:21 ` Carsten Dominik
2009-04-16 13:09 ` Chris Gray
2009-04-16 20:47 ` Carsten Dominik
2009-04-19 19:55 ` Chris Gray
2009-04-20 6:04 ` Carsten Dominik
2009-05-02 7:27 ` Carsten Dominik
2009-05-04 7:52 ` Chris Gray
2009-05-04 14:28 ` Carsten Dominik [this message]
2009-05-06 14:01 ` Chris Gray
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=C1719B25-961D-4C20-B543-8C5D66E699F1@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=chrismgray@gmail.com \
--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
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).