From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: Buffer local alias?
Date: Wed, 15 Jan 2014 10:50:57 +0100 [thread overview]
Message-ID: <87k3e1y3ni.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 8661plbnde.fsf@somewhere.org
Hello Sebastien,
"Sebastien Vauban" <sva-news@mygooglest.com>
writes:
> Hello Andreas,
>
> Andreas Leha wrote:
>> The drop of the implicit naming of call lines, for example, was (and
>> still will be for some of my files) a bigger issue.
>
> Could you remind me what's the problem you're talking of?
Evaluating a #+call line used to produce a result block named with the
name of the called code block and the arguments used. That is not the
case any more.
Something like (off the top of my head):
--8<---------------cut here---------------start------------->8---
#+call: foo(bar=1)
#+call: foo(bar=2)
#+results: foo(bar=1)
| the | results |
#+results: foo(bar=2)
| the | results |
--8<---------------cut here---------------end--------------->8---
Now, one has to name the call line to get a named results block.
I would not call it a problem, though. The change just meant that I had
to introduce a lot of names for call lines in some of my files where I
relied on that implicit naming of results.
I know, that I have not adapted all affected files of mine. So, if ever
I wanted to re-export these, I will need to do some more naming of call
lines...
All the best,
Andreas
next prev parent reply other threads:[~2014-01-15 9:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 19:00 Buffer local alias? Thomas S. Dye
2014-01-14 19:39 ` Nick Dokos
2014-01-14 19:44 ` Bastien
2014-01-14 20:12 ` Thomas S. Dye
2014-01-14 21:49 ` Andreas Leha
2014-01-15 0:05 ` Thomas S. Dye
2014-01-15 8:41 ` Andreas Leha
2014-01-15 8:51 ` Eric S Fraga
2014-01-15 9:33 ` Sebastien Vauban
2014-01-15 9:50 ` Andreas Leha [this message]
2014-01-15 19:59 ` Achim Gratz
2014-01-15 20:40 ` Andreas Leha
2014-01-16 16:44 ` Achim Gratz
2014-01-16 16:54 ` Rick Frankel
2014-01-16 17:51 ` Thomas S. Dye
2014-01-15 9:30 ` Sebastien Vauban
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k3e1y3ni.fsf@med.uni-goettingen.de \
--to=andreas.leha@med.uni-goettingen.de \
--cc=emacs-orgmode@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.