I'm doing a major update of the optimx package and things were going relatively
smoothly until this weekend when files that have passed win-builder gave NOTEs
on r-devel for several manual (.Rd) files.
The NOTE is of the form
* checking Rd files ... NOTE
checkRd: (-1) fnchk.Rd:40-41: Lost braces
On Sun, 22 Oct 2023 10:43:08 -0400
J C Nash wrote:
>\itemize{
> \item{fnchk OK;}{ \code{excode} = 0;
> \code{infeasible} = FALSE}
The \item command inside \itemize{} lists doesn't take arguments.
Did you mean \describe{} instead of \itemize{}?
--
Best r
I ran into the same issue last week with .Rd files that were
previously accepted on CRAN and concluded that the package checks are
becoming more critical about this aspect of Rd syntax, which is good.
To reproduce the note outside R-devel and by that identify which files
in your package are affect
Thanks. That seems to be the issue. Also vincent's suggestion of checkRd.
JN
On 2023-10-22 10:52, Ivan Krylov wrote:
On Sun, 22 Oct 2023 10:43:08 -0400
J C Nash wrote:
\itemize{
\item{fnchk OK;}{ \code{excode} = 0;
\code{infeasible} = FALSE}
The \
Hi,
My package is failing on linux based systems because of an attempt to write in
a location of package. One of the core features that we would like user to have
is to modify the values in the config file, for which package has a function
for user to provide modified config. In future, they sh
On Sun, 22 Oct 2023 16:52:50 +
"Keshav, Krishna" wrote:
> My package is failing on linux based systems because of an attempt to
> write in a location of package. One of the core features that we
> would like user to have is to modify the values in the config file
Can you place the edited con
Installed packages may not be modified because they are permitted to be
installed with read-only access. You have no option to proceed in this
direction.
Configuration files are normally stored in the user's working directory.
Dotfiles are a common convention in *nix operating systems, but in W
