From: Achim Gratz <Stromeko@Nexgo.DE>
To: emacs-orgmode@gnu.org
Subject: Re: #+call split into multiple lines?
Date: Fri, 29 Mar 2013 08:18:43 +0100 [thread overview]
Message-ID: <kj3f6f$t5o$1@ger.gmane.org> (raw)
In-Reply-To: <BB05EBB7-FD8A-4390-A3C7-652695C6479E@nf.mpg.de>
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 :-)
prev parent reply other threads:[~2013-03-29 7:17 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
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 [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='kj3f6f$t5o$1@ger.gmane.org' \
--to=stromeko@nexgo.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).