A github search might be helpful to identify packages that define macros in
their Rd files:
https://github.com/search?utf8=%E2%9C%93&q=user%3Acran+extension%3Ard+newcommand&type=Code
On Thu, Nov 9, 2017 at 6:35 PM, Rolf Turner wrote:
>
> On 10/11/17 12:00, Duncan Murdoch wrote:
>
> [Rolf Turner
To follow up, I managed to remove the warning by exporting the
function directly. In other words, my NAMESPACE now contains both:
export("[")
exportMethods("[")
could someone please confirm it's really the best approach?
thanks!
-- François
On Tue, Apr 18, 2
Hello all,
With R-devel, I see the following for one of my packages
(https://github.com/fmichonneau/phylobase), and I would appreciate any
insights on what needs to be adjusted to fix it:
Functions or methods with usage in documentation object
'subset-methods' but not in code:
[
Thanks!
--
Hi Bill,
The problem is not with the warning() function but with your if()
test that triggers the warning. It probably has something to do with
slight differences in rounding. I suggest you use debug() or browser()
on each platform to see why your condition is TRUE or FALSE.
Cheers,
-- Fran
Hello all,
On win-builder (both with R 3.2.3 and R-devel), I see this error at the
end of the check.log. Would anyone have any hint on what might be wrong and
possible ways of debugging? I obviously can't reproduce this on my Linux
systems.
The vignette is built to HTML with knitr as the engi
Hello all,
As I can only easily access computers with Linux, I am very grateful
for the existence of win-builder to test my packages with Windows.
Today I encountered an issue with win-builder that took me a while
to figure out. My package was failing unit tests on win-builder but I
couldn't
