emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Mikhail Titov" <mlt@gmx.us>
To: 'Eric Schulte' <eric.schulte@gmx.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [babel] Why #+name: is not a member of params?
Date: Tue, 5 Jun 2012 19:53:50 -0500	[thread overview]
Message-ID: <006301cd437e$d7405430$85c0fc90$@us> (raw)
In-Reply-To: <87txypqnip.fsf@gmx.com>

> -----Original Message-----
> From: Eric Schulte [mailto:eric.schulte@gmx.com]
> Sent: Tuesday, June 05, 2012 7:42 PM
> To: Mikhail Titov
> Cc: emacs-orgmode@gnu.org
> Subject: Re: [O] [babel] Why #+name: is not a member of params?
> 
> "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))
> >
> ...
> 
> 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

Thank you, Eric!

Marvelous! It does what I want. I see its definition in ob.el .

M. 

      reply	other threads:[~2012-06-06  1:01 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
2012-06-06  0:53   ` Mikhail Titov [this message]

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='006301cd437e$d7405430$85c0fc90$@us' \
    --to=mlt@gmx.us \
    --cc=emacs-orgmode@gnu.org \
    --cc=eric.schulte@gmx.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).