Hi,
The nucleoSim package has duplicate commits dating from long time (older than
October 2016).
I have checked the package by doing a fresh clone directly from Bioconductor
and those duplicate commits seem to be present there.
Can you confirm that it is the case and if so, provide
On Wed, Apr 10, 2019 at 5:06 AM, Tomas Kalibera
wrote:
>> This is my first post here. I came across the very same problem.
>> It can be reproduced within modified tests/Embedding/RParseEval.c
>
> Please check https://www.r-project.org/posting-guide.html and update
> your post if you still need
Hi -
During the last build, the man page received some warnings, I’m not sure what I
am doing wrong. The items are nestled within the argument tag and the curly
braces are in place.
Found the following significant warnings: Warning:
/home/biocbuild/bbs-3.9-bioc/meat/PoTRA/man/potra_man.Rd:25:
Thanks Hervé,
I also found this tweet by John Muschelli useful for this situation
https://twitter.com/StrictlyStat/status/1103303028751372289 where he
suggests using suppressWarnings(RNGversion("3.5.0"))
That's what I did for example in
On 10/04/2019 12:32 p.m., Jeroen Ooms wrote:
On Wed, Apr 10, 2019 at 5:45 PM Duncan Murdoch wrote:
On 10/04/2019 10:29 a.m., Yihui Xie wrote:
Since it is "technically easy" to disable the best fit conversion and
the best fit is rarely good, how about providing an option for
code/package
On Wed, Apr 10, 2019 at 5:45 PM Duncan Murdoch wrote:
>
> On 10/04/2019 10:29 a.m., Yihui Xie wrote:
> > Since it is "technically easy" to disable the best fit conversion and
> > the best fit is rarely good, how about providing an option for
> > code/package authors to disable it? I'm asking
Yes, again in a script sourced by source(encoding = ...). But also by
typing it directly in R console.
Most of the time, I use RStudio as a front-end. For this experiment, I
also verified it in Rgui. In both front-ends, it behaves completely in
the same way.
An optional parameter to source()
On 10/04/2019 10:29 a.m., Yihui Xie wrote:
Since it is "technically easy" to disable the best fit conversion and
the best fit is rarely good, how about providing an option for
code/package authors to disable it? I'm asking because this is one of
the most painful issues in packages that may need
If the charset choice is intentional, then we can add a builder/docker
image for this on R-hub.
It would certainly make sense to have a builder with an unusual charset.
Gabor
On Wed, Apr 10, 2019 at 11:43 AM David Gohel wrote:
>
> Dear all,
>
> Among the CRAN machines used by Check,
Since it is "technically easy" to disable the best fit conversion and
the best fit is rarely good, how about providing an option for
code/package authors to disable it? I'm asking because this is one of
the most painful issues in packages that may need to source() code
containing UTF-8 characters
On 4/10/19 1:14 PM, Jeroen Ooms wrote:
On Wed, Apr 10, 2019 at 12:19 PM Tomáš Bořil wrote:
Minimalistic example:
Let's type "ř" (LATIN SMALL LETTER R WITH CARON) in RGui console:
"ř"
[1] "r"
Although the script is in UTF-8, the characters are replaced by
"simplified" substitutes
On Wed, Apr 10, 2019 at 12:19 PM Tomáš Bořil wrote:
>
> Minimalistic example:
> Let's type "ř" (LATIN SMALL LETTER R WITH CARON) in RGui console:
> > "ř"
> [1] "r"
>
> Although the script is in UTF-8, the characters are replaced by
> "simplified" substitutes uncontrollably (depending on OS
On 4/10/19 10:22 AM, Tomáš Bořil wrote:
> Hello,
>
> There is a long-lasting problem with processing UTF-8 source code in R
> on Windows OS. As Windows do not have "UTF-8" locale and R passes
> source code through OS before executing it, some characters are
> "simplified" by the OS before
Dear all,
Among the CRAN machines used by Check, "r-devel-linux-x86_64-debian-clang" has
been upgraded from UTF-8 to ISO8859-15.
# using R Under development (unstable) (2019-04-07 r76333)
# using platform: x86_64-pc-linux-gnu (64-bit)
# using session charset: ISO8859-15
I realized that while
Hello,
There is a long-lasting problem with processing UTF-8 source code in R
on Windows OS. As Windows do not have "UTF-8" locale and R passes
source code through OS before executing it, some characters are
"simplified" by the OS before processing, leading to undesirable
changes.
Minimalistic
On 4/5/19 8:14 AM, Mikhail Titov wrote:
Hello!
This is my first post here. I came across the very same problem.
It can be reproduced within modified tests/Embedding/RParseEval.c
Please check https://www.r-project.org/posting-guide.html and update
your post if you still need to get help here
16 matches
Mail list logo
