From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Rainer M Krug <Rainer@krugs.de>
Cc: Org-mode <emacs-orgmode@gnu.org>,
"Charles C. Berry" <ccberry@ucsd.edu>,
"Thomas S. Dye" <tsd@tsdye.com>,
Rainer M Krug <r.m.krug@gmail.com>
Subject: Re: ob-R, problem with try/catch
Date: Mon, 04 May 2015 21:03:33 +0200 [thread overview]
Message-ID: <87pp6gyxkq.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <m2a8xkd9k8.fsf@krugs.de> (Rainer M. Krug's message of "Mon, 04 May 2015 10:35:35 +0200")
Hello,
Rainer M Krug <Rainer@krugs.de> writes:
> Thinking about it, I don't think that the combinations should be defined
> in the linting library, but in the language definition (ob-XXX.el), by a
> function which returns all tested combinations, i.e. all combinations
> which have been tested, including if they work or not. The linting
> library could then query these lists and use them.
>
> This would keep the language definition in the ob-XXX.el file and make
> it easier to maintain.
This is already the case. See, e.g., `org-babel-header-args:R' and
`org-babel-common-header-args-w-values'.
The linting library doesn't hard-code any combination anymore.
Regards,
--
Nicolas Goaziou 0x80A93738
next prev parent reply other threads:[~2015-05-04 19:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 22:03 ob-R, problem with try/catch Thomas S. Dye
2015-04-23 2:23 ` Charles C. Berry
2015-04-23 5:40 ` Rainer M Krug
2015-04-23 15:53 ` Thomas S. Dye
2015-04-23 16:20 ` Rainer M Krug
2015-04-23 16:42 ` Aaron Ecay
2015-04-23 16:13 ` Charles C. Berry
2015-04-23 16:29 ` Rainer M Krug
2015-04-23 17:11 ` Thomas S. Dye
2015-04-23 22:39 ` Aaron Ecay
2015-04-23 23:36 ` Thomas S. Dye
2015-04-26 12:49 ` Nicolas Goaziou
2015-04-26 17:11 ` Charles C. Berry
2015-04-26 17:28 ` Nicolas Goaziou
2015-05-04 8:35 ` Rainer M Krug
2015-05-04 19:03 ` Nicolas Goaziou [this message]
2015-04-23 6:35 ` Thomas S. Dye
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=87pp6gyxkq.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=Rainer@krugs.de \
--cc=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=r.m.krug@gmail.com \
--cc=tsd@tsdye.com \
/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).