Gábor Csárdi

``` r roxygen2::roc_proc_text(roxygen2::rd_roclet(), " #' Foo #' @name foo #' #' @md #' @param foo #' * A #' * B #' * C NULL ") #> $foo.Rd #> %...

Since the white space is significant for markdown, maybe we should just not trim it at all? In some cases like this, at least. The specific problem here is that...

The whitespace conveys information in markdown, so if you cut it off then you lose that information. We could cut off _some_ of it, like `glue::trim()`. This would make sense...

> two kinds of whitespaces in a roxy markdown How do you tell the difference? E.g. what kind of whitespace is this? ```r #' @section Mysection: #' myfun() #' myfun2()...

> I think using first indent as in glue to infer the indent space is reasonable and predictable. Yes, but I think it is also not necessary. The best is...

> unindented roxy documentation is poor practice You can still indent it, in a way that works with markdown. E.g. your original post is perfectly fine. :) > Or perhaps...

There is ``` Roxygen: list(packages = "foobar") ``` now. Isn't that good?

Is that because you need to attach the package? I am fairly sure that the loading works.

We can attach `packages` then maybe?

Use `options(error = recover)` and then try to find more info interactively in the roxygen2 frames.