From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rainer M Krug Subject: Re: Writing .el files for org in org? Date: Thu, 22 May 2014 10:12:09 +0200 Message-ID: References: <87lhturac1.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57781) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WnO6w-0000fg-Hf for emacs-orgmode@gnu.org; Thu, 22 May 2014 04:12:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WnO6r-0008Aq-DO for emacs-orgmode@gnu.org; Thu, 22 May 2014 04:12:22 -0400 Received: from mail-wg0-f49.google.com ([74.125.82.49]:46715) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WnO6r-0008Ai-6t for emacs-orgmode@gnu.org; Thu, 22 May 2014 04:12:17 -0400 Received: by mail-wg0-f49.google.com with SMTP id m15so3065886wgh.20 for ; Thu, 22 May 2014 01:12:16 -0700 (PDT) Received: from Rainers-MacBook-Pro-3.local (arn78-1-88-186-171-7.fbx.proxad.net. [88.186.171.7]) by mx.google.com with ESMTPSA id go1sm6636548wib.7.2014.05.22.01.12.14 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 May 2014 01:12:15 -0700 (PDT) In-Reply-To: <87lhturac1.fsf@gmail.com> (Aaron Ecay's message of "Wed, 21 May 2014 19:25:37 -0400") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Aaron Ecay 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=20 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=20 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:=20 [1] https://github.com/rkrug/orgmode-dev [2] https://github.com/rkrug/ess-dev =2D-=20 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 --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBAgAGBQJTfbFdAAoJENvXNx4PUvmCFEMH/jja79gb2X6GcwnUNPOziey5 GvOrZkBCcxc1isijcQun5/28x/yhwjX+i4ARQCcZNGexQvXpViQHAdXSnpDWLCRW KNX9CmRLGlJqI25BtZP8CDP988YNasdRklGQb3byVSHOC+lCKhCk1nC6r4SHTo+J bJzkHzkEW2cRQ2y8WmXnb21W3/8+1AGXwyTTFMtDd+FRrZm1ewS1vICFIP5NMidK 2rQoI0/8Os9Kx9iyTS2fvc7nIY2glapOPi2ecrxClV/t3v5q63O5DOCvBoeTf6oo jCivUTNrQoSiyC3sBo2O9dO9kNQBZvRSkc4cSnzahjVebZhKSK3f6yBGQpvaeg8= =mw1p -----END PGP SIGNATURE----- --=-=-=--