-
Notifications
You must be signed in to change notification settings - Fork 235
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Global roxygen options for a package #507
Comments
I see you are finishing things up. I'll try to write this tomorrow. |
I'd also consider turning markdown on by default, and we can see how it goes when applied to my packages. |
Of course you would turn it on, because you can blame me if sg goes wrong. With the current link implementation, there will be problems with Rd Why don't we just turn it on for your packages? Regardless, we need this global switch, I think. I'll write it tonight. On 21 Sep 2016 19:55, "Hadley Wickham" notifications@github.com wrote:
|
Wait a sec, there is code for this already: https://github.com/klutometis/roxygen/blob/596893c42b48aaa91781a60ffaad3c2dc0000ac0/R/roxygenize.R#L86 I am sorry, I wasn't aware of this. So I can just all markdown here..... |
* Global options from Roxygen: in DESCRIPTION, for #507 Also add the @nomd tag. * Test cases for turning markdown on/off globally * Turn on markdown for roxygen2 itself * Update markdown vignette for new global option & @nomd * Fix wrong entry in NEWS file * Add relevant issues to NEWS file, markdown entry * markdown NEWS: mention global flag, @md @nomd
This can be closed, there is a way, the |
We would put them in the
DESCRIPTION
file, in theRoxygen
field, which is allowed, but not used currently.The plan is to have R code there, and initially we would support switching Markdown parsing on/off:
I will submit a PR in the coming days.
The text was updated successfully, but these errors were encountered: