Org-mode mailing list
 help / color / mirror / Atom feed
From: (Дядов Васил Стоянов)
To: Nicolas Goaziou <>
Subject: Re: Bug: [PATCH] Org-babel: separate #+attr_... for code block and for results block [7.9.3d (release_7.9.3d-834-g60083a.dirty @ /home/vdyadov/Work/Tools/emacs/org-mode/lisp/)]
Date: Thu, 24 Jan 2013 11:58:17 +0400
Message-ID: <> (raw)
In-Reply-To: <> (Nicolas Goaziou's message of "Wed, 23 Jan 2013 16:22:24 +0100")


Nicolas Goaziou <> writes:

> Affiliated keywords have to be put above elements they refer to, without
> a blank line in-between.


> Elements doesn't care about order for affiliated keywords (here results
> and attr_html), but Babel, which isn't built on Elements (yet), does.
> Hence, I suggest:
>   #+attr_html: ...
>   #+results: ...
>   file

With my patch to ob-core.el org-babel works fine with your suggestion. It
just skips #+attr_...: lines as blank lines (original behaviour of
org-babel is to skip blank lines between #+end_src and #+results, when
it searches results block for updating). Of course, org-babel behavior
may be easily changed to dissallow empty lines between #+attr_...: and

But currently org-elements allows next construction:

| #+attr_html: alt="big image" width="100%"
|  ^ 
|  |
|  +- several empty lines between attr and file
|  |
|  v
| file:123.png

That is why I think that it is not necessary to make org-babel behavior
different from org-elements (to dissalow empty lines between #+attr and
#+results when it searches results block), at least for now.

PS: Is there any good documentation and explanation of org-mode
internals? I could help a little with rewritting org-babel to use

With best regards,

  reply	other threads:[~2013-01-24  7:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 11:43 Дядов Васил Стоянов
2013-01-23 13:15 ` Nicolas Goaziou
2013-01-23 15:03   ` Дядов Васил Стоянов
2013-01-23 15:22     ` Nicolas Goaziou
2013-01-24  7:58       ` Дядов Васил Стоянов [this message]
2013-01-24  7:59         ` Bastien
2013-01-24 13:20         ` Nicolas Goaziou
2013-01-24 14:10           ` Дядов Васил Стоянов
2013-01-24 14:13             ` Bastien

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Org-mode mailing list

This inbox may be cloned and mirrored by anyone:

	git clone --mirror list/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 list list/ \
	public-inbox-index list

Example config snippet for mirrors.
Newsgroups are available over NNTP:

AGPL code for this site: git clone