From: Rainer M Krug <Rainer@krugs.de>
To: Bastien <bzg@gnu.org>
Cc: Aaron Ecay <aaronecay@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Writing .el files for org in org?
Date: Thu, 22 May 2014 11:54:51 +0200 [thread overview]
Message-ID: <m2iooy2l5g.fsf@krugs.de> (raw)
In-Reply-To: <87vbsy88lk.fsf@bzg.ath.cx> (Bastien's message of "Thu, 22 May 2014 11:29:27 +0200")
[-- Attachment #1: Type: text/plain, Size: 1863 bytes --]
Bastien <bzg@gnu.org> writes:
> Rainer M Krug <Rainer@krugs.de> writes:
>
>> 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.
>
> But there is still the first and main problem that Aaron pointed to.
Just to make my point clear: I would not see the .org file as the one
which is used when using org, but as the one which is used to
1) understand what is going on, i.e. include more detailed explanations
of what the functions are doing, what they are returning, possibly some
callcharts of the functions --- just everything to really understand
what is going on and why these things are done as they are. In other
words: follow the paradigm of literate programming.
2) which is tangled to generate the ob-....el file
3) which then can be debugged as usual
4) and if it is working, detangled into ob-....org
I must stress this comes from somebody not familiar with to much
emacs-lisp, but very familiar with R and Pascal (long time ago) and some
working C knowledge.
So the reason why I think it would be advantageous to have these files
in org does not lie with the programmer familiar with emacs-lisp, but
with somebody familiar with the other side.
Cheers,
Rainer
--
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 9:55 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
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 [this message]
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=m2iooy2l5g.fsf@krugs.de \
--to=rainer@krugs.de \
--cc=aaronecay@gmail.com \
--cc=bzg@gnu.org \
--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).