From: Bastien <bzg@gnu.org>
To: Rainer M Krug <Rainer@krugs.de>
Cc: Aaron Ecay <aaronecay@gmail.com>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: Writing .el files for org in org?
Date: Sun, 27 Jul 2014 23:50:20 +0200 [thread overview]
Message-ID: <87d2cp75wd.fsf@bzg.ath.cx> (raw)
In-Reply-To: <m2egz7e7i3.fsf@krugs.de> (Rainer M. Krug's message of "Mon, 02 Jun 2014 16:00:36 +0200")
Hi John and Rainer,
Rainer M Krug <Rainer@krugs.de> writes:
>> What if we created a new directory in the repository called "org" which
>> contains these kinds of files? It would be analogous to the "lisp"
>> directory. I don't think we need to have both ob-R.org and ob-R.el in the
>> repository.
>
> I think that would be a very good idea for certain modules like your
> org-ref and ob-R I am working on.
Maybe you could use such a "load-flow" for a while, see if it is
robust enough, and if so, we could move on and have it in the repo?
My gut feeling is that it will bring some issues, so experimenting
before would be nice.
--
Bastien
next prev parent reply other threads:[~2014-07-28 17:25 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
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 [this message]
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=87d2cp75wd.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=Rainer@krugs.de \
--cc=aaronecay@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
/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).