From: Aaron Ecay <aaronecay@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [RFC] [PATCH] [parser] org-element.el: Handle block parameters
Date: Wed, 30 Oct 2013 00:28:42 -0400 [thread overview]
Message-ID: <8738njcrgl.fsf@gmail.com> (raw)
In-Reply-To: <878uxca3p6.fsf@gmail.com>
Hi Nicolas,
2013ko urriak 29an, Nicolas Goaziou-ek idatzi zuen:
[...]
>> This brings the parser in line with the Org Syntax as documented on
>> Worg: <http://orgmode.org/worg/dev/org-syntax.html#Greater_Blocks>.
>
> Besides this reason (which could also be solved by updating Org Syntax
> document), do you have a need for this extension?
I have several export filters which translate special blocks into latex
code (doing some tedious string munging in elisp, such that a simple
latex block is not warranted; I also have the eventual goal of making
them cross-backend, which will involve a different bit of tedious
munging). These filters take arguments in the #+begin_foo line.
I also think it would be nice for the org code following this paragraph
to be translated to output that makes sense for each backend, with the
quote’s author formatted nicely (on a new line preceded by a dash,
aligned to the right margin in text/html, using the csquotes package in
latex, etc.). This patch would enable such a functionality.
#+begin_quote Chico Marx
Why a duck?
#+end_quote
If these seem like compelling use cases, then I will make the
adjustments you proposed to the code (which all look correct).
Thanks,
--
Aaron Ecay
next prev parent reply other threads:[~2013-10-30 4:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 19:04 [RFC] [PATCH] [parser] org-element.el: Handle block parameters Aaron Ecay
2013-10-29 8:20 ` Nicolas Goaziou
2013-10-30 4:28 ` Aaron Ecay [this message]
2013-10-30 8:01 ` Nicolas Goaziou
2013-10-30 22:23 ` Aaron Ecay
2013-10-31 11:00 ` Nicolas Goaziou
2013-10-31 18:15 ` Aaron Ecay
2013-10-31 19:08 ` Nicolas Goaziou
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=8738njcrgl.fsf@gmail.com \
--to=aaronecay@gmail.com \
--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).