From: Rainer M Krug <r.m.krug@gmail.com>
To: Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: [babel] Writing R-packages the org way?
Date: Fri, 8 Oct 2010 17:41:31 +0200 [thread overview]
Message-ID: <AANLkTimvOzWtcUupz6_FFviukuotZsibmf-uXoV+x7NS@mail.gmail.com> (raw)
In-Reply-To: <t5x8w2825ml.fsf@rgc.damtp.cam.ac.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1632 bytes --]
On Fri, Oct 8, 2010 at 3:09 PM, Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk>wrote:
>
>
>
> Dan Davison <davison@stats.ox.ac.uk> writes:
>
> > Hi Chuck,
> >
> > I agree about making use of existing ESS tools and that a more
> > traditional Org approach might be appropriate.
>
> this may be slightly off-topic, but another way of adding documentation
> is to the 'roxygen' markup.
> http://roxygen.org/
Actually not - I did not specify that I want to use .Rd .
>
> ESS has some support for editing roxygen comment chunks within ESS
> buffers,
>
Yes - I looked into Roxygen some time ago, but in the context of org, I see
it as not necessary to include the documentation in the source code block -
when using
#+begin_src Rd
#+end_src
and
#+begin_src R
#+end_src
I can nicely separate these two on the code level - but in the org file,
they are still literate programming.
Cheers,
Rainer
> Stephen
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
--
NEW GERMAN FAX NUMBER!!!
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology,
UCT), Dipl. Phys. (Germany)
Centre of Excellence for Invasion Biology
Natural Sciences Building
Office Suite 2039
Stellenbosch University
Main Campus, Merriman Avenue
Stellenbosch
South Africa
Cell: +27 - (0)83 9479 042
Fax: +27 - (0)86 516 2782
Fax: +49 - (0)321 2125 2244
email: Rainer@krugs.de
Skype: RMkrug
Google: R.M.Krug@gmail.com
[-- Attachment #1.2: Type: text/html, Size: 3124 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-10-08 15:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 14:02 [babel] Writing R-packages the org way? Rainer M Krug
2010-10-07 14:24 ` Erik Iverson
2010-10-07 15:03 ` Dan Davison
2010-10-07 15:12 ` Erik Iverson
2010-10-07 15:59 ` Dan Davison
2010-10-07 16:18 ` Rainer M Krug
2010-10-07 16:04 ` Rainer M Krug
2010-10-07 17:16 ` Dan Davison
2010-10-08 4:29 ` Charles C. Berry
2010-10-08 12:10 ` Dan Davison
2010-10-08 13:09 ` Stephen Eglen
2010-10-08 15:41 ` Rainer M Krug [this message]
2010-10-08 15:35 ` Rainer M Krug
2010-10-07 14:25 ` Dan Davison
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=AANLkTimvOzWtcUupz6_FFviukuotZsibmf-uXoV+x7NS@mail.gmail.com \
--to=r.m.krug@gmail.com \
--cc=S.J.Eglen@damtp.cam.ac.uk \
--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).