On Wed, 22 May 2019, Lionel Henry wrote:
> Hi Martin,
>
>> On 22 May 2019, at 03:50, Martin Maechler wrote:
>>
>> I'm pretty sure that all teaching and documentation about S and R
>> has suggested that print(f) and auto-printing should result in
>> the same output _ AFAIR also for S4 objects
L
More to the point: the custom search function is currently broken anyway - it
just gives me 404.
Should we just get rid of it? If people want to use Google they can just say
site:developer.r-project.org foo
> On May 22, 2019, at 1:08 AM, Paul Menzel wrote:
>
> [Please CC me on replies, as
[Please CC me on replies, as I am not subscribed.]
Dear R folks,
Accessing the *R Developer Page* [1], the browser (Firefox) shows an
HTTPS warning.
The reason is the embedded Google logo.
Gemischte (unsichere) Anzeige-Inhalte von
"http://www.google.com/logos/Logo_40wht.gif"; werden auf e
suspendInterrupts has dynamic extent, so you need to make sure it
covers the entire computation. Defining your f like this is one option:
f <- function() {
ff <- function() {
on.exit(cntr_on.exit <<- cntr_on.exit + 1L)
cntr_f <<- cntr_f + 1L
## allowInterrupts(... i
Hi Martin,
> On 22 May 2019, at 03:50, Martin Maechler wrote:
>
> I'm pretty sure that all teaching and documentation about S and R
> has suggested that print(f) and auto-printing should result in
> the same output _ AFAIR also for S4 objects
I agree with the principle that autoprint and pri
> Martin Maechler
> on Wed, 22 May 2019 09:50:10 +0200 writes:
> William Dunlap
> on Tue, 21 May 2019 12:11:45 -0700 writes:
>> Letting a user supply the autoprint function would be nice also. In a
way
>> you can already do that, using addTaskCallback(), but th
Hi,
Is there currently any way to guarantee that on.exit does not fail to execute
the recorded expression because of a user interrupt arriving during function
exit? Consider:
f <- function() {
suspendInterrupts({
on.exit(suspendInterrupts(cntr_on.exit <<- cntr_on.exit + 1L))
cntr_f <<
> William Dunlap
> on Tue, 21 May 2019 12:11:45 -0700 writes:
> Letting a user supply the autoprint function would be nice also. In a way
> you can already do that, using addTaskCallback(), but that doesn't let you
> suppress the standard autoprinting.
> Having the d
