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

From: Nicolas Goaziou <n.goaziou@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [RFC] [PATCH] [parser] org-element.el: Handle block parameters
Date: Wed, 30 Oct 2013 09:01:06 +0100	[thread overview]
Message-ID: <87iowfb325.fsf@gmail.com> (raw)
In-Reply-To: <8738njcrgl.fsf@gmail.com> (Aaron Ecay's message of "Wed, 30 Oct 2013 00:28:42 -0400")

Hello,

Aaron Ecay <aaronecay@gmail.com> writes:

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

IIRC, I already suggested a solution with Babel for this problem.
There's no need to complicate core Org syntax for such a specific case.

> 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

Well actually, this kind of syntax is confusing at best. Something like
the following could be used instead:

  #+begin_quote :author Chico Marx

Actually, there are two points to consider:

  1. Providing something like :author implies that all back-ends in core
     and contrib and the manual have to be updated accordingly.

  2. "parameters" is too vague to be useful. It needs to be parsed
     further, which means that we must define explicitly use cases and
     keywords. Thus, I don't think adding "parameters" to every block is
     a good move if we don't know beforehand how they will be used.

     Though, it is possible to extend the syntax to well-defined
     specific cases. :author may be one of them, there are certainly
     others.


Regards,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2013-10-30  8:01 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
2013-10-30  8:01     ` Nicolas Goaziou [this message]
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=87iowfb325.fsf@gmail.com \
    --to=n.goaziou@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

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