From: Bastien <bzg@gnu.org>
To: Rainer M Krug <Rainer@krugs.de>
Cc: Aaron Ecay <aaronecay@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Writing .el files for org in org?
Date: Thu, 22 May 2014 13:04:15 +0200 [thread overview]
Message-ID: <8738g2krbk.fsf@bzg.ath.cx> (raw)
In-Reply-To: <m2iooy2l5g.fsf@krugs.de> (Rainer M. Krug's message of "Thu, 22 May 2014 11:54:51 +0200")
Rainer M Krug <Rainer@krugs.de> writes:
> 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.
Sorry I was too terse in my previous answer: I completely agree with
the goal you describe, but I don't think adding an .org source along
the .el output (say e.g. ob-R.org and ob-R.el) will simplify my life
as a maintainer: each time an ob-*.org file is changed we need to
tangle it again... and this leads to auto-tangling, auto-committing
considerations that I don't even want to start thinking about.
--
Bastien
next prev parent reply other threads:[~2014-05-22 11:04 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
2014-05-22 11:04 ` Bastien [this message]
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=8738g2krbk.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=Rainer@krugs.de \
--cc=aaronecay@gmail.com \
--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).