From: Dan Davison <davison@stats.ox.ac.uk>
To: "Charles C. Berry" <cberry@tajo.ucsd.edu>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>,
Rainer M Krug <r.m.krug@gmail.com>
Subject: Re: [babel] Writing R-packages the org way?
Date: Fri, 08 Oct 2010 13:10:09 +0100 [thread overview]
Message-ID: <87fwwglwbi.fsf@stats.ox.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.1010071949470.29985@tajo.ucsd.edu> (Charles C. Berry's message of "Thu, 7 Oct 2010 21:29:59 -0700")
Hi Chuck,
I agree about making use of existing ESS tools and that a more
traditional Org approach might be appropriate.
> If you do decide to go all in for a 'one org file makes one package'
> approach, you might try to get Rd language support added, so you can
> edit Rd directly in an Org Src buffer in Rd-mode.
No extra code is needed to get editing support for languages.
#+begin_src XXX
provides an edit buffer in XXX-mode automatically, with no special
customization. Also fontification in the org buffer works automatically
if `org-src-fontify-natively' is set.
Dan
> And get
> org-babel-Rd-evaluate to run Rd-preview-help or call Rd2HTML or
> whatnot.
>
> HTH,
>
> Chuck
>
>> Then, to insert a template, you can use
>>
>> #+call: R-pkg-template(function_name="do.something") :results output org raw
>>
>> which should give something like this:
>>
>> --8<---------------cut here---------------start------------->8---
>> #+results: R-pkg-template(function_name="do.something")
>> * do.something
>> ** Help
>> *** Title
>> this is do.something title
>> *** Description
>> do.something does this...
>> *** Usage
>> do.something(arg1, arg2, ...)
>> *** Arguments
>> arg1: the first argument
>> *** Examples
>> do.something(arg1 = x, arg2 = y)
>> ** Definition
>> begin_src R :tangle R/package.R
>> do.something <- function(arg1, arg2) {
>>
>> }
>> --8<---------------cut here---------------end--------------->8---
>>
>> While playing about you may want to get rid of the "raw" directive so
>> that the results will automatically be replaced on repeated evaluations.
>>
>> Dan
>>
>>>
>>>
>>>
>>>>
>>>>>> Any suggestions how to best proceed?
>>>>>>>
>>>>>>> Dream: I would like to have one org file which contains everything
>>>>>>> (documentation, code, other relevant files) and if I export or
>>>>>>> tangle the file, I have the package ready.
>>>>>>>
>>>>>> Well, that functionality is essentially present with code blocks
>>>>>> and tangling, except the documentation part.
>>>>>>
>>>>>
>>> Exactly - and that is the part I would like to have.
>>>
>>>
>>>>
>>>>> Hi Erik,
>>>>>
>>>>> Would you mind expanding on that -- what are we missing for the
>>>>> documentation part?
>>>>>
>>>>>
>>>> Dan, by "except for the documentation part", I meant generating
>>>> .Rd files (the LaTeX-like syntax) automatically from some org-syntax
>>>> that does *not* depend on code blocks. I.e., it would be cool to
>>>> specify syntax like I have above for documentation. Using org-mode
>>>> headlines for each section like Description, Usage, Arguments, etc.
>>>>
>>>> Just like exporting to LaTeX generates sections, some process would
>>>> use these headlines to generate the .Rd sections.
>>>>
>>>> That way, you don't have to use the .Rd syntax yourself. No big deal,
>>>> just a convenience feature. I don't know how you'd specify to org-mode
>>>> that a particular subtree was to generate .Rd syntax, and I don't know
>>>> if it would be on export or tangling.
>>>>
>>>> An alternative is simply just to use code blocks of type Rd within
>>>> org-mode and then tangle to .Rd files. That's what I currently do.
>>>>
>>>> Hope that explains it,
>>>> Erik
>>>>
>>>>
>>>> Dan
>>>>>
>>>>
>>
>> _______________________________________________
>> 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
>>
>
> Charles C. Berry (858) 534-2098
> Dept of Family/Preventive Medicine
> E mailto:cberry@tajo.ucsd.edu UC San Diego
> http://famprevmed.ucsd.edu/faculty/cberry/ La Jolla, San Diego 92093-0901
>
>
>
> _______________________________________________
> 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 12:10 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 [this message]
2010-10-08 13:09 ` Stephen Eglen
2010-10-08 15:41 ` Rainer M Krug
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=87fwwglwbi.fsf@stats.ox.ac.uk \
--to=davison@stats.ox.ac.uk \
--cc=cberry@tajo.ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=r.m.krug@gmail.com \
/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).