Re: Writing .el files for org in org?

[Rainer M Krug <Rainer@krugs.de>]

[-- Attachment #1: Type: text/plain, Size: 2484 bytes --]

Bastien <bzg@gnu.org> writes:

> Hi Rainer and Aaron,
>
> Aaron Ecay <aaronecay@gmail.com> writes:
>
>> 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.
>
> My point of view too.
>
> On top of this, I see two problems:
>
> 1. there is the problem of minimizing the distance between what the
>    Org repository contains and what goes into the Emacs repository*
>
> 2. and the problem of imposing something that might not fit all
>    contributors.  Using litterate programming for a few files but not
>    all is not a good option, and using litterate programming for all
>    files would be too much of a constraint for many...

I see you point concerning using org files for all files, but the
ob-LANGUAGE.el files are in their own class (LANGUAGE refers to e.g. R,
sh, ...). 

1) Many users of these features will have (at least a little)
programming experience, not unlikely more in LANGUAGE then in emacs-lisp.

2) the functions in these files are the actual interface between the
LANGUAGE and org, and it is more important here that they can be
understood and changes suggested by their users then in the org core
files, as specialist users of a specific LANGUAGE might discover problems, of
which the original author might not be aware of or which have been
introduced by updates in LANGUAGE.

So I would argue that in ob-LANGUAGE.el files the non-elisp-expert is more
likely to look and work then in the core org files wherefore an
a more familiar interface for these changes (literate programming in
org) would provide more advantages then in the org-core files.

Cheers,

Rainer

>
> Best,
>
> * That's also the reason why I'm skeptical about having the manual
>   written as org.org instead of org.texi -- I mean, I'd be glad to be
>   able to edit the manual as org.org, but having a preliminary export
>   step before importing org.texi into Emacs might create problems.

-- 
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 --]