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

From: Eric Schulte <eric.schulte@gmx.com>
To: Mikhail Titov <mlt@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: [babel] Why #+name: is not a member of params?
Date: Tue, 05 Jun 2012 18:42:22 -0600	[thread overview]
Message-ID: <87txypqnip.fsf@gmx.com> (raw)
In-Reply-To: <006001cd437a$03917d70$0ab47850$@us> (Mikhail Titov's message of "Tue, 5 Jun 2012 19:19:17 -0500")

"Mikhail Titov" <mlt@gmx.us> writes:

> Hello!
>
> I’d like to insert a comment into tangle output with a block name. I thought I could easily access it (like from org-babel-expand-body:XXX function) with
>
> (cdr (assq :name params))
>
> But apparently it does not work. When I do C-c C-v C-v trying to expand body, I get nil as it is not there.
>
> Did I miss something?
>
> I want that so each block appears in individual Matlab code cell [1].
>
> [1] http://www.mathworks.com/help/techdoc/matlab_env/brqxeeu-259.html
>
> Mikhail
>

Hi Mikhail,

The code block name is not a member of params.  Params only holds header
arguments, not other meta data like the name.  The code block name is
stored in the `info' list which is active while the code block is being
processed, so you could access it with something like the following,
although which is relying on an implementation detail that is not part
of the formal spec (i.e., cheating) and could change.

#+name: foo
#+begin_src emacs-lisp
  (nth 4 info)
#+end_src

#+RESULTS: foo
: foo

Best,

-- 
Eric Schulte
http://cs.unm.edu/~eschulte

next prev parent reply	other threads:[~2012-06-06  0:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-06  0:19 [babel] Why #+name: is not a member of params? Mikhail Titov
2012-06-06  0:42 ` Eric Schulte [this message]
2012-06-06  0:53   ` Mikhail Titov

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=87txypqnip.fsf@gmx.com \
    --to=eric.schulte@gmx.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mlt@gmx.us \
    /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).