From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [RFC] Block switches as #+HEADER: args?
Date: Tue, 02 Sep 2014 12:01:29 +0200 [thread overview]
Message-ID: <87y4u2pchy.fsf@gmail.com> (raw)
In-Reply-To: 87bnqymk3n.fsf@nicolasgoaziou.fr
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Hello,
>
> Thorsten Jolitz <tjolitz@gmail.com> writes:
>
>> and at least in the 2nd case the switches are lost, because they don't
>> work as header args:
>
> [...]
>
>> #+HEADER: -n
>> #+BEGIN_EXAMPLE
>> Hallo World
>> whats up?
>> #+END_EXAMPLE
>
> This is not valid syntax. Switches are to be put on the block line.
> Only header arguments can be put on a #+HEADER line. See
>
> (info "(Org) Structure of code blocks")
>
> in particular the difference between switches and header arguments.
Thats what I thought, but wouldn't it be nicer to treat switches and
header args more uniformly here? E.g allow something like:
#+HEADER: :switches -n
#+BEGIN_EXAMPLE
Hallo World
whats up?
#+END_EXAMPLE
Otherwise custom solutions are needed to store the switches in some
place when nuking the surrounding #+begin/#+end lines in a conversion
process, and restore them again when converting back to Org. Or the
switches-info is simply lost during conversion.
--
cheers,
Thorsten
next prev parent reply other threads:[~2014-09-02 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 9:35 [RFC] Block switches as #+HEADER: args? Thorsten Jolitz
2014-09-02 9:45 ` Nicolas Goaziou
2014-09-02 10:01 ` Thorsten Jolitz [this message]
2014-09-02 10:33 ` Nicolas Goaziou
2014-09-02 11:07 ` Thorsten Jolitz
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=87y4u2pchy.fsf@gmail.com \
--to=tjolitz@gmail.com \
--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).