From: vdyadov@elvees.com (Дядов Васил Стоянов)
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
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 [thread overview]
Message-ID: <s4ysj5rovvq.fsf@canopus-pc.elvees.com> (raw)
In-Reply-To: <871udbapqn.fsf@gmail.com> (Nicolas Goaziou's message of "Wed, 23 Jan 2013 16:22:24 +0100")
Hi,
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> Affiliated keywords have to be put above elements they refer to, without
> a blank line in-between.
Ok.
> 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
#+results:.
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
org-elements.
With best regards,
Vasil
next prev parent 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 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/)] Дядов Васил Стоянов
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:
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=s4ysj5rovvq.fsf@canopus-pc.elvees.com \
--to=vdyadov@elvees.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).