emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Stefan Vollmar <vollmar@nf.mpg.de>
To: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: #+call split into multiple lines?
Date: Thu, 28 Mar 2013 21:49:22 +0100	[thread overview]
Message-ID: <BB05EBB7-FD8A-4390-A3C7-652695C6479E@nf.mpg.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 2030 bytes --]

Hallo,

I am a new Org-Babel convert (thanks, Nicolas!) and our first project replaces a MACRO (raw HTML template) with 12+ arguments and is a major improvement as we can now use named arguments.

This short example works:

#+call: mhead-hcard(cname="Dr. Stefan Vollmar",gname="Stefan",prefix="Dr.",web="stefan-vollmar.html",photo="stefan-vollmar.jpg") :results html

However, this only uses only four of 12+ arguments and - from my point of view - already suffers from being written in one line.

We have listed some of our attempts to increase readability (none of them works with release_8.0-pre-193-gaa7b1e).

(1) "natural" multi-line

#+call: mhead-hcard(
cname="Dr. Stefan Vollmar",   # full name for title
gname="Stefan",               # given name 
photo="stefan-vollmar.jpg",   # can be jpg or png
...)

(2) Attempt in keeping with a multi-line #+header construct

#+call: mhead-hcard(
#+call:  cname="Dr. Stefan Vollmar",   # full name for headline
#+call:  gname="Stefan",               # given name 
#+call:  photo="stefan-vollmar.jpg",   # can be jpg or png
...

(3) Using a "line continuation marker"

#+call: mhead-hcard(
 cname="Dr. Stefan Vollmar",\
 gname="Stefan",\
 photo="stefan-vollmar.jpg",\
...)

Maybe even with optional comments:

#+call: mhead-hcard(
 cname="Dr. Stefan Vollmar",\  # full name for headline
 gname="Stefan",\              # given name 
 photo="stefan-vollmar.jpg",\  # can be jpg or png
...)

Maybe there already is a good solution to increase readability? Maybe the "line continuation marker" (3) would be a general solution for all cases in org where now no line breaks are possible?

Many thanks for any help with this.
Warm regards,
 Stefan
-- 
Dr. Stefan Vollmar, Dipl.-Phys.
Head of IT group
Max-Planck-Institut für neurologische Forschung
Gleueler Str. 50, 50931 Köln, Germany
Tel.: +49-221-4726-213  FAX +49-221-4726-298
Tel.: +49-221-478-5713  Mobile: 0160-93874279
E-Mail: vollmar@nf.mpg.de   http://www.nf.mpg.de




[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 4409 bytes --]

             reply	other threads:[~2013-03-28 20:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-28 20:49 Stefan Vollmar [this message]
2013-03-28 21:17 ` #+call split into multiple lines? Thomas S. Dye
2013-03-28 21:27   ` Sebastien Vauban
2013-03-28 21:51     ` Thomas S. Dye
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=BB05EBB7-FD8A-4390-A3C7-652695C6479E@nf.mpg.de \
    --to=vollmar@nf.mpg.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 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).