<div>I don't think so. I use a makefile that executes `roxygen` directly through R and passes all the options I need:</div><div><br></div><div> <a href="https://github.com/Sharpie/RTikZDevice/blob/master/Makefile#L69">https://github.com/Sharpie/RTikZDevice/blob/master/Makefile#L69</a></div>
<div><br></div><div>-Charlie</div><div><br></div>On Sat, Jul 23, 2011 at 3:16 PM, Jeroen Ooms <span dir="ltr"><<a href="mailto:jeroen.ooms@stat.ucla.edu" target="_blank">jeroen.ooms@stat.ucla.edu</a>></span> wrote:<br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Can I do this through R CMD roxygen as well?<br>
<div><div></div><div><br>
<br>
<br>
On Sun, Jul 24, 2011 at 12:12 AM, Charlie Sharpsteen<br>
<<a href="mailto:chuck@sharpsteen.net" target="_blank">chuck@sharpsteen.net</a>> wrote:<br>
> On Sat, Jul 23, 2011 at 2:42 PM, Jeroen Ooms <<a href="mailto:jeroen.ooms@stat.ucla.edu" target="_blank">jeroen.ooms@stat.ucla.edu</a>><br>
> wrote:<br>
>><br>
>> Is there a directive that I can use to exclude functions from being<br>
>> parsed by roxygen? I have a package which defines a lot of functions,<br>
>> but only 2 are exported. I would only like to generate documentation<br>
>> for these two functions.<br>
>><br>
>> However it seems roxygen automatically generated Rd files for all<br>
>> functions in the R folder. This is especially problematic because it<br>
>> chokes on some methods that I define for a class that is defined in<br>
>> another package. I would rather have that it only parses functions<br>
>> with an @export directive.<br>
>><br>
>> Thanks.<br>
><br>
> Try passing the argument `use.Rd2=TRUE` when calling `roxygenize`. Then<br>
> Roxygen will skip any function that is not preceded by documentation<br>
> comments ` #' `.<br>
> -Charlie<br>
</div></div></blockquote></div><br>