From: Rainer M Krug <Rainer@krugs.de>
To: emacs-orgmode@gnu.org
Subject: Re: Writing .el files for org in org?
Date: Thu, 22 May 2014 10:12:09 +0200 [thread overview]
Message-ID: <m2d2f644h2.fsf@krugs.de> (raw)
In-Reply-To: <87lhturac1.fsf@gmail.com> (Aaron Ecay's message of "Wed, 21 May 2014 19:25:37 -0400")
[-- Attachment #1: Type: text/plain, Size: 2314 bytes --]
Aaron Ecay <aaronecay@gmail.com> writes:
> Hi Rainer,
>
> I have wondered about what you suggest as well, from the point of view
> of trying to modify the long pieces of R code which are embedded in
> strings in ob-R.el. I think this would be easier if they could be
> tangled from R code blocks in an org file. So from that point of view
> the idea has a +1 from me.
That is one aspect am looking at (independent of the org file question)
at the moment, to make the R code more configurable. My approach is to
a) have it in a emacs string variables which can be customized, or
b) in an R file which is loaded and used instead of the definition in
the variable. If you are interested, please see my org [1] and ess [2]
which, at the moment, have to be used together, as I am "outsourcing"
the loading at the moment to ESS.
Concerning putting them in an org file, I don't see a real advantage
here, unless the ob-R.el is also in an org file.
>
> I am not so convinced that having all the elisp code in an org file
> would be convenient, since I am worried that would break the interactive
> features of elisp programming. (edebug, find-function, paredit, ...).
> But if you are doing the experiment, I would be glad to see what you
> come up with: the benefits might turn out to be worth the potential
> drawbacks.
I am not thinking about having the org files used for actual running
org, but rather as a tool to write the code. The workflow would be then:
1) in the org file, write the code for ob-R.el including documentation
2) tangle the file to ob-R.el
3) debug ob-R.el - in R
4) untangle the edits back into the ob-R.org file
5) done
So the tools for debugging would be still working on the .el file.
Rainer
>
> --
> Aaron Ecay
Footnotes:
[1] https://github.com/rkrug/orgmode-dev
[2] https://github.com/rkrug/ess-dev
--
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany)
Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa
Tel : +33 - (0)9 53 10 27 44
Cell: +33 - (0)6 85 62 59 98
Fax : +33 - (0)9 58 10 27 44
Fax (D): +49 - (0)3 21 21 25 22 44
email: Rainer@krugs.de
Skype: RMkrug
PGP: 0x0F52F982
[-- Attachment #2: Type: application/pgp-signature, Size: 494 bytes --]
next prev parent reply other threads:[~2014-05-22 8:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 20:21 Writing .el files for org in org? Rainer M Krug
2014-05-21 23:25 ` Aaron Ecay
2014-05-22 8:12 ` Rainer M Krug [this message]
2014-05-22 8:56 ` Bastien
2014-05-22 9:25 ` Rainer M Krug
2014-05-22 9:29 ` Bastien
2014-05-22 9:54 ` Rainer M Krug
2014-05-22 11:04 ` Bastien
2014-05-22 11:42 ` Rainer M Krug
2014-05-22 15:10 ` Bastien
2014-05-23 7:29 ` Rainer M Krug
2014-06-02 11:22 ` John Kitchin
2014-06-02 14:00 ` Rainer M Krug
2014-07-27 21:50 ` Bastien
2014-07-30 2:04 ` John Kitchin
2014-05-22 15:44 ` Josh Berry
2014-05-22 18:49 ` Rainer M Krug
2014-05-22 0:30 ` Grant Rettke
2014-05-22 8:30 ` Rainer M Krug
2014-05-22 23:34 ` Grant Rettke
2014-05-27 8:45 ` Thorsten Jolitz
2014-05-27 9:07 ` Rainer M Krug
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=m2d2f644h2.fsf@krugs.de \
--to=rainer@krugs.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).