Dear Frederik,
I can confirm that especially the first issue on your list (resizing the
terminal) has "bothered me" badly for some time now: I'm on Ubuntu
(usually).
Göran Broström
On 2016-05-13 00:23, frede...@ofb.net wrote:
Hi Peter, Martin, and others,
Thanks for your replies.
- The b
On 12/05/2016 9:21 PM, Spencer Graves wrote:
Hello:
Is it widely known that objects not explicitly deleted from one
vignette in a package can be available to a second in "R CMD build" and
"R CMD check" but not when the second vignette is built manually, at
least under RStudio on Mac OS
Actually, I think both Martin and I use reaadline R versions on a daily basis
(Linux and OSX Terminal respectively). For my case, it is just that I rarely
use the backwards search feature and I'm old enough that terminal widths other
than 80 look odd to me so I don't resize much either. Of cours
>
> on Thu, 12 May 2016 15:23:04 -0700 writes:
> Hi Peter, Martin, and others,
> Thanks for your replies.
> - The bugs apply to all systems that use GNU Readline, not just Linux
> or Arch Linux.
yes... but
> - Readline version 6.3 changed the signal handling s
On 12.05.2016 09:51, Martin Maechler wrote:
> My ulimit package exposes this API ([1], should finally submit it to
> CRAN); unfortunately this very API seems to be unsupported on OS X
> [2,3]. Last time I looked into it, neither of the documented settings
> achieved the desire
Hello:
I could use help understanding an error reported by "R CMD build
sos" that's new with R 3.3.0:
Error in texi2dvi(file = file, pdf = TRUE, clean = clean, quiet = quiet, :
Running 'texi2dvi' on 'sos.tex' failed.
LaTeX errors:
! Undefined control sequence.
l.1 \Sconcordance
On 13/05/2016 10:41 AM, Spencer Graves wrote:
Hello:
I could use help understanding an error reported by "R CMD build
sos" that's new with R 3.3.0:
Error in texi2dvi(file = file, pdf = TRUE, clean = clean, quiet = quiet, :
Running 'texi2dvi' on 'sos.tex' failed.
LaTeX errors:
! U
That, for example, complex(real=NaN) and complex(imaginary=NaN) are regarded as
equal makes it possible that length(unique(as.character(x))) >
length(unique(x)) (current code of function 'factor' doesn't expect it). Yes,
an argument for the behavior is that NA and NaN are of one kind.
On my sys
Hi Martin,
I think this is a general problem with any function that does dispatch
on ... - I think for well-defined behaviour you always need to
dispatch on pairs, folding/reducing (like in your code) to get a
single value. The downside of this approach is obviously performance:
for n inputs, you
