From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: switch parsing in babel
Date: Mon, 28 Mar 2016 08:36:22 -0400 [thread overview]
Message-ID: <m2egaueq49.fsf@Johns-MacBook-Air.local> (raw)
In-Reply-To: <87wponq8hr.fsf@nicolasgoaziou.fr>
Nicolas Goaziou writes:
> Hello,
>
> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
>> I am trying to make a new source block that looks like this:
>>
>> #+BEGIN_SRC obabel -icml -osmi
>> [CH4]
>> #+END_SRC
>>
>> This gets parsed to:
>>
>> (src-block
>> (:language "obabel" :switches "-i" :parameters "cml -osmi" :begin
>> 190 :end 240 :number-lines nil :preserve-indent t :retain-labels
>> t :use-labels t :label-fmt nil :hiddenp nil :value "[CH4]
>> \n" :post-blank 1 :post-affiliated 190 :parent nil))
>>
>> Is that correct? I would have thought that
>> 1. The first switch should be -icml
>> 2. -osmi would also be a switch.
>
> This is incorrect, but not in the way you think.
>
> There is no concatenation for switches in Org syntax, so it should be
> parsed as
>
> :switches nil :parameters -icml -osmi
>
> which looks wrong anyway.
>
> Maybe you're simply mis-using switches here, which are reserved to Org?
It could be. I get it now, I was looking at
http://orgmode.org/guide/Working-With-Source-Code.html
#+NAME: <name>
#+BEGIN_SRC <language> <switches> <header arguments>
<body>
#+END_SRC
and I just noticed that "<switches> can be used to control export of the
code block" which isn't what I was trying to do with it.
>
>
> Regards,
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
prev parent reply other threads:[~2016-03-28 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-27 23:17 switch parsing in babel John Kitchin
2016-03-28 9:04 ` Nicolas Goaziou
2016-03-28 12:36 ` John Kitchin [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=m2egaueq49.fsf@Johns-MacBook-Air.local \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).