Re: [Rd] Possible bug, max argument in print.default(), on R-3.5.1-patched

2018-09-25 Thread Martin Maechler
> peter dalgaard > on Mon, 24 Sep 2018 10:16:07 +0200 writes: > Not in print.default(), but in print.data.frame(), which > is now doing its own max= handling but not passing max to > print.default (maechler, r75122 --- was this really for > r-patched? -pd Yes, becaus

Re: [Rd] Possible bug, max argument in print.default(), on R-3.5.1-patched

2018-09-24 Thread peter dalgaard
Not in print.default(), but in print.data.frame(), which is now doing its own max= handling but not passing max to print.default (maechler, r75122 --- was this really for r-patched? -pd > On 22 Sep 2018, at 23:46 , Gábor Csárdi wrote: > > The max argument of print.default() does not override

[Rd] Possible bug, max argument in print.default(), on R-3.5.1-patched

2018-09-22 Thread Gábor Csárdi
The max argument of print.default() does not override options(max.print), see below. R 3.5.1 and R-devel both seem good. Gábor > options(max.print = 1) > print(data.frame(a=1:10)) a 1 1 [ reached 'max' / getOption("max.print") -- omitted 9 rows ] > print(data.frame(a=1:10), max = 100) a