emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] #+call split into multiple lines?


From: Achim Gratz
Subject: Re: [O] #+call split into multiple lines?
Date: Fri, 29 Mar 2013 08:18:43 +0100
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4

Am 28.03.2013 21:49, schrieb Stefan Vollmar:
(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
...)

This doesn't parse well, so I venture to guess that Nicolas wouldn't like that.

(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
...

See perhaps http://permalink.gmane.org/gmane.emacs.orgmode/68027 (unanswered so far and was actually meant to solve a different cosmetic problem).

(3) Using a "line continuation marker"

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

See (1).

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
...)

The comments would still be part of the arguments, so a special form of trimming would be needed.

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?

Line continuation markers are only really useful with line-by-line evaluation or if the whole buffer gets preprocessed, so they are not a good solution for Org, IMHO.


Regards,
--
Achim.

(on the road :-)




reply via email to

[Prev in Thread] Current Thread [Next in Thread]