From: tsd@tsdye.com (Thomas S. Dye)
To: Sebastien Vauban
<public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: #+call split into multiple lines?
Date: Thu, 28 Mar 2013 11:51:03 -1000 [thread overview]
Message-ID: <m1obe3w5vc.fsf@poto.westell.com> (raw)
In-Reply-To: <86ip4bw6yd.fsf@somewhere.org> (Sebastien Vauban's message of "Thu, 28 Mar 2013 22:27:38 +0100")
Aloha Seb,
"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
> Hi Thomas,
>
> Thomas S. Dye wrote:
>> In this situation I often put the arguments in a named Org table and
>> then write the Babel source code block to take a single argument--the
>> table name--and parse the information passed in that way.
>>
>> #+name: card-table
>> | cname | gname | photo | etc.|
>> | Dr. Stefan Vollmar | Stefan | stefan-vollmar.jpg | ... |
>> | Dr. Stefan Vollmar, Jr. | Stefan Jr. | stefan-vollmar-jr.jpg | ... |
>>
>>
>> #+call: mhead-hcard(card=card-table[0,]) for Stefan
>>
>> #+call: mhead-hcard(card=card-table[1,]) for Stefan Jr.
>>
>> If you don't mind writing some extra code for the Babel function, then
>>
>> #+call: mhead-hcard(card=card-table,gname="Stefan")
>>
>> etc.
>
> And do you eventually have a way to write a "for-loop" for all the lines of
> the tables, not being forced to write as many calls as the number of lines you
> do have?
>
> I don't see (immediately) how to do such, but that would really allow to
> promote such a use case!
Not sure I understand your question. Perhaps I misunderstood Stefan's
use case?
There are several languages supported by Babel that have loop
constructs. I was assuming that Stefan would use one of these when I
suggested the possibility of writing some extra code.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2013-03-28 21:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 20:49 #+call split into multiple lines? Stefan Vollmar
2013-03-28 21:17 ` Thomas S. Dye
2013-03-28 21:27 ` Sebastien Vauban
2013-03-28 21:51 ` Thomas S. Dye [this message]
2013-03-29 8:24 ` Stefan Vollmar
2013-03-29 9:25 ` Achim Gratz
2013-03-29 9:34 ` feng shu
2013-03-29 2:33 ` Eric Abrahamsen
2013-03-29 2:43 ` Thomas S. Dye
2013-03-29 3:14 ` Eric Abrahamsen
2013-03-29 7:18 ` Achim Gratz
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=m1obe3w5vc.fsf@poto.westell.com \
--to=tsd@tsdye.com \
--cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
--cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.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 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).