From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: link abbreviation with multiple params, e. g. for geo locations
Date: Fri, 07 Jun 2013 22:10:20 +0200 [thread overview]
Message-ID: <87zjv165sj.fsf@Rainer.invalid> (raw)
In-Reply-To: CALn3zogvL86WmS2XNaiRUM-wEtL6_d5FMh0qNaaTOHbLy5X6fg@mail.gmail.com
Michael Brand writes:
> But for me it would have helped to have some other name, containing
> neither "src-block", which I associate it with #+BEGIN_SRC but
> not #+CALL line or inline call_<name>, nor "head", which I associate
> with #+HEADER.
There are multiple places in Babel where "src-block-head" means "the
header arguments to a Babel invocation". You'd have to look at the
history when separate header lines and inline calls were introduced, but
I think you'll find the reason for the naming somewhere in the past.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
next prev parent reply other threads:[~2013-06-07 20:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 17:03 link abbreviation with multiple params, e. g. for geo locations Michael Brand
2013-05-29 16:14 ` Michael Brand
2013-06-05 17:19 ` Michael Brand
2013-06-06 17:01 ` Eric Schulte
2013-06-07 14:53 ` Michael Brand
2013-06-07 15:18 ` Eric Schulte
2013-06-07 19:16 ` Michael Brand
2013-06-07 19:54 ` Vitalie Spinu
2013-06-08 18:05 ` Eric Schulte
2013-06-08 18:52 ` Vitalie Spinu
2013-06-08 19:21 ` Eric Schulte
2013-06-14 17:54 ` Michael Brand
2013-06-14 18:18 ` Eric Schulte
2013-06-14 20:13 ` Michael Brand
2013-06-19 9:39 ` Michael Brand
2013-06-07 20:10 ` Achim Gratz [this message]
2013-06-08 18:03 ` Eric Schulte
2013-06-09 7:56 ` Michael Brand
2013-06-09 8:07 ` Michael Brand
2013-06-09 19:18 ` Eric Schulte
2013-06-09 20:32 ` Michael Brand
2013-06-11 13:12 ` Eric Schulte
-- strict thread matches above, loose matches on Subject: below --
2013-05-05 15:06 Michael Brand
2013-05-06 7:06 ` Christian Moe
2013-05-06 18:42 ` Michael Brand
2013-05-06 22:29 ` Christian Moe
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=87zjv165sj.fsf@Rainer.invalid \
--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 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.