Dear all,
justify argument is hard coded in format.ftable:
cbind(apply(LABS, 2L, format, justify = "left"),
apply(DATA, 2L, format, justify = "right"))
It would be useful to have the possibility to modify the argument between
c("left", "right", "centre", "none") as in format.default.
On 10.05.2020 23:26, Sapphire Zhou wrote:
I met a problem when I uploaded the package to CRAN. There is a warning told me
“All user-level objects in a package should have documentation entries.”
Actually, those functions are not user-level functions. How could I claim
non-user-level
1. Don't export them.
2. Use: \keyword{ internal } in the .Rd file
>From "Writing R Extensions"
"The special keyword ‘internal’ marks a page of internal objects that
are not part of the package’s API. If the help page for object foo has
keyword ‘internal’, then help(foo) gives this help page,
I met a problem when I uploaded the package to CRAN. There is a warning told me
“All user-level objects in a package should have documentation entries.”
Actually, those functions are not user-level functions. How could I claim
non-user-level functions in an R package.
Is there any idea to
Hello,
I am a maintainer on the LightGBM project, focused on that project's R
package. The R package is not available on CRAN yet (we are working on it),
so for now our users must build it from source.
The package includes compilation of a C++ library, and we link to R.dll /
R.so to use
> On Sunday, May 10, 2020, 12:24:17 PM EDT, Lionel Henry
> wrote:
>
> The main reason for resetting the tagbuf in `print.default()` and
> other entry points to the print routine is that it is currently not
> reset on exit. Creating a context to reset it on exit to its last
> value might work.
Hello,
The main reason for resetting the tagbuf in `print.default()` and
other entry points to the print routine is that it is currently not
reset on exit. Creating a context to reset it on exit to its last
value might work. This should be done in the entry points rather than
in print-value-rec
Currently S3 objects nested in generic vectors cause the tag buffer to be
reset. This feels sub-optimal for those objects that don't have a print method:
> list(a=list(b='hello'))
$a
$a$b ### notice "$a$b"
[1] "hello"
> list(a=structure(list(b='hello'), class='world'))
$a
