emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: New tutorial on using Emacs lisp for Org spreadsheet formulas
Date: Wed, 01 Feb 2012 13:39:50 +0100	[thread overview]
Message-ID: <87mx92sp61.fsf@gmail.com> (raw)
In-Reply-To: <87pqdzt6em.fsf@Rainer.invalid> (Achim Gratz's message of "Wed, 01 Feb 2012 07:27:29 +0100")

Hello,

Achim Gratz <Stromeko@nexgo.de> writes:

> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>> I don't see what is clumsy with affiliated keywords.
>
> Well, you write the arguments before starting the source block, getting
> everything wardbacks (and I don't think that's easier to parse, but you
> would know better(*)).

I think you're mixing src blocks and Babel. A src block contains,
fontifies and allows to edit source code. Babel arguments (or caption,
or name) are meta-data that applies to the whole src block element, not
to its contents.

> Last but not least I can never remember if any of the "#+" stuff is
> supposed to end with a ":"

Affiliated keywords all do. If one doesn't, it's a bug.

> and whether it wants another ":" in front of the arguments or not.

That's another topic, and I agree that, at one point or another, we'll
have to unify the way parameters are written. IMO, Babel usage is a good
standard.

> (*) Reminds me I'll have to try what happens if I write header
> arguments that are detached from the source block.  Devious, I know,
> but the manual does not really specify anything.

But Org elements does. Affiliated keywords must be attached to their
relative element.

> If you look carefully, that source block above does not contain a
> drawer.  It has a (hypothetical) associated multiline header argument
> that happens to look and feel like a drawer.

Then it's a duck.

>> Though, drawers can contain src-blocks.
>
> Is there any specification that they must fully contain them?

You may want to read comments in org-element.el. I also posted some
explanations when I announced the library.

> Anyway, that was just an idea and if nobody likes it, that's fine with
> me, too.

I just wanted to let you know that the idea of putting "quasi-drawers"
within a src-block is against the model described by the current parser.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2012-02-01 12:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-31 17:33 Bastien
2012-01-31 18:33 ` Achim Gratz
2012-01-31 19:31   ` Nicolas Goaziou
2012-01-31 20:01     ` Achim Gratz
2012-01-31 20:55       ` Nicolas Goaziou
2012-02-01  6:27         ` Achim Gratz
2012-02-01 12:39           ` Nicolas Goaziou [this message]
2012-02-01  6:10     ` Jude DaShiell
2012-01-31 22:29   ` Carsten Dominik
2012-02-01  6:37     ` Achim Gratz
2012-02-01  6:56       ` Carsten Dominik
2012-02-01  7:03       ` Bastien
2012-02-01 17:29         ` Achim Gratz
2012-02-01  7:14     ` Bastien
2012-02-01 15:39 ` Eric S Fraga

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=87mx92sp61.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=Stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: New tutorial on using Emacs lisp for Org spreadsheet formulas' \
    /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 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).