Note that the spell checks are not run by default in R CMD check. To
trigger these, you need to set the (undocumented) environment variable
_R_CHECK_CRAN_INCOMING_USE_ASPELL_=TRUE
and have aspell (or alternatives) installed.
No worries about a potential pain of rechecking the same flagged
That's an excellent idea. I can't resist pointing out that everything
that was flagged this morning has been in those packages for years (and
for multiple submissions), and has never been flagged before. So I would
still have to update my master last this time around. And a human at
CRAN would
I have a list of words, acronyms and initialisms that commonly get flagged
as misspelled words when I submit updates. I generally just put an
explanation for each one in the "optional comment" section of the
submission form. It's pretty simple and seems to work out well.
On Fri, Jul 16, 2021 at
For what it's worth, I didn't see your message as aggressive. But
that's email: it's hard to know the impressions people will get from it.
Regarding your point, I'd like to say (unaggressively!) that it's not
your problem if the CRAN folks choose differently than you would in how
they
Hi Jeff,
I think you are inferring an attitude in my initial message that wasn't
actually present. I greatly appreciate the hard work that CRAN
maintainers put in on behalf of the community. And I really did (and do)
want to understand why some of their valuable volunteer time should be
Spelling has different importance to different people. You are expressing a
value judgement that differs from the values of R Core, but are presenting your
opinion as if they are facts. My point is that your challenging attitude IMO
makes having a conversation about those concerns difficult. (I
Hi,
I have been updating a couple of R packages this morning. One of them
triggered a manual inspection for "possibly mis-spelled words in
DESCRIPTION" for my last name (Coombes) --- even though none of the
other 20 packages that I maintain has ever triggered that particular
NOTE. A second
