From @eb@meyer @end|ng |rom |@u@de  Tue Nov  7 23:59:29 2023
From: @eb@meyer @end|ng |rom |@u@de (Sebastian Meyer)
Date: Tue, 7 Nov 2023 23:59:29 +0100
Subject: [Rd] 
 False positives in check for lost braces (in tools::checkRd())
In-Reply-To: <8513a24e-e435-4781-aca2-452097961468@mx.uni-saarland.de>
References: <8513a24e-e435-4781-aca2-452097961468@mx.uni-saarland.de>
Message-ID: <8304b64d-9048-456a-8ecb-ec207a9bf273@fau.de>

This is a known issue already reported to the Rdpack maintainer. In some 
cases, the Rd code generated by Rdpack's macros contains unnecessary 
braces that trigger the check note because they match the pattern 
"text{text}" that detects common mistakes like "code{x}" (missing an 
escape for the macro name).

Rdpack's fork of tools::deparseLatex() is being updated to drop the 
braces that cause the note. I have modified the check code to ignore 
these cases for now (r85491).

Best regards,

	Sebastian Meyer


Am 07.11.23 um 17:13 schrieb Martin Becker:
> Dear developers,
> 
> while preparing to submit a package to CRAN, I noticed that a check for
> lost braces in Rd files (which is enabled in the current r-devel when
> checking with the '--as-cran' option) seems to return false positives.
> 
> More specifically, a 'Lost braces' NOTE is issued (at least sometimes)
> when using the \insertRef{...}{...} command from the Rdpack package.
> 
> Since the corresponding changes in r-devel seem to be quite recent
> (apparently as of r85196), I hope this sketchy report is sufficient to
> track down the problem. If not, I will try to create a reproducible example.
> 
> Best regards and many thanks,
> Martin
> 
>



[Rd] False positives in check for lost braces (in tools::checkRd())
Sebastian Meyer