edit() doubles backslashes when keep.source=TRUE

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

edit() doubles backslashes when keep.source=TRUE

R devel mailing list
Is it just my installation or does edit() (or fix(), etc.) in R-4.0.0
double all the backslashes when options(keep.source=TRUE)?  E.g.,

> options(keep.source=TRUE)
> f <- function(x) { cat("\t", x, "\n", sep="") }
> edit(f) # exit the editor without making any changes
The editor (vi or notepad) shows doubled backslashes
    function(x) { cat("\\t", x, "\\n", sep="") }
as does the return value of edit().

If I set options(keep.source=FALSE) before defining 'f' or remove t's
'srcref' attribute then the backslashes are left alone.

Bill Dunlap
TIBCO Software
wdunlap tibco.com

        [[alternative HTML version deleted]]

______________________________________________
[hidden email] mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Reply | Threaded
Open this post in threaded view
|

Re: edit() doubles backslashes when keep.source=TRUE

Sebastian Meyer-4
I can confirm this changed behaviour. I just compared R-3.6.3 with
yesterday's R-devel. Using R-devel, the tempfile opened by the editor
(Emacs for me, but shouldn't matter) contains doubled backslashes.

This could be related to

https://bugs.r-project.org/bugzilla/show_bug.cgi?id=17800

Best regards,

        Sebastian


Am 15.05.20 um 03:50 schrieb William Dunlap via R-devel:

> Is it just my installation or does edit() (or fix(), etc.) in R-4.0.0
> double all the backslashes when options(keep.source=TRUE)?  E.g.,
>
>> options(keep.source=TRUE)
>> f <- function(x) { cat("\t", x, "\n", sep="") }
>> edit(f) # exit the editor without making any changes
> The editor (vi or notepad) shows doubled backslashes
>     function(x) { cat("\\t", x, "\\n", sep="") }
> as does the return value of edit().
>
> If I set options(keep.source=FALSE) before defining 'f' or remove t's
> 'srcref' attribute then the backslashes are left alone.
>
> Bill Dunlap
> TIBCO Software
> wdunlap tibco.com
>
> [[alternative HTML version deleted]]
>
> ______________________________________________
> [hidden email] mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
>

______________________________________________
[hidden email] mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Reply | Threaded
Open this post in threaded view
|

Re: edit() doubles backslashes when keep.source=TRUE

Martin Maechler
>>>>> Sebastian Meyer
>>>>>     on Fri, 15 May 2020 10:47:55 +0200 writes:

    > I can confirm this changed behaviour. I just compared R-3.6.3 with
    > yesterday's R-devel. Using R-devel, the tempfile opened by the editor
    > (Emacs for me, but shouldn't matter) contains doubled backslashes.

    > This could be related to

        > https://bugs.r-project.org/bugzilla/show_bug.cgi?id=17800

Yes, indeed, I'm sure this is the same; an inadvertent bug indeed.

    > Best regards,
    > Sebastian

... and  "just the usual"

<whining>

    Why does nobody anymore  help R development by working with
    "R-devel", or at least then the alpha, beta and the "RC"
    (Release Candidate) versions that we release daily for about one
    month before the final release?

    Notably a highly staffed enterprise such as Rstudio (viz the bug
    report 17800 above), but also others could really help by
    starting to use the "next version" of R on a routine basis ...

<whining/>

Still: Thank you, of course,
 Bill Dunlap, and Sebastian and Jonathan (PR 17800)

Martin

    > Am 15.05.20 um 03:50 schrieb William Dunlap via R-devel:
    >> Is it just my installation or does edit() (or fix(), etc.) in R-4.0.0
    >> double all the backslashes when options(keep.source=TRUE)?  E.g.,
    >>
    >>> options(keep.source=TRUE)
    >>> f <- function(x) { cat("\t", x, "\n", sep="") }
    >>> edit(f) # exit the editor without making any changes
    >> The editor (vi or notepad) shows doubled backslashes
    >> function(x) { cat("\\t", x, "\\n", sep="") }
    >> as does the return value of edit().
    >>
    >> If I set options(keep.source=FALSE) before defining 'f' or remove t's
    >> 'srcref' attribute then the backslashes are left alone.
    >>
    >> Bill Dunlap
    >> TIBCO Software
    >> wdunlap tibco.com

______________________________________________
[hidden email] mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Reply | Threaded
Open this post in threaded view
|

Testing before release (was: edit() doubles backslashes when keep.source=TRUE)

Duncan Murdoch-2
On 15/05/2020 9:41 a.m., Martin Maechler wrote:
[ deletions ]

> <whining>
>
>      Why does nobody anymore  help R development by working with
>      "R-devel", or at least then the alpha, beta and the "RC"
>      (Release Candidate) versions that we release daily for about one
>      month before the final release?
>
>      Notably a highly staffed enterprise such as Rstudio (viz the bug
>      report 17800 above), but also others could really help by
>      starting to use the "next version" of R on a routine basis ...
>
> <whining/
I understand the whining, bugs that get released are embarrassing.  But
when I read the NEWS, I can see that both the NEW FEATURES and BUG FIXES
sections of x.y.0 releases tend to be much longer than the BUG FIXES
sections in patch releases.  That seems to indicate that things are
working reasonably well.

For a really rough measure, just counting bullet points:

R 4.0.0:  65 new features, 55 bug fixes

R 3.6.3:  1 new feature, 7 bug fixes

R 3.6.2:  2 new features, 21 bug fixes

R 3.6.1:  0 new features, 16 bug fixes

R 3.6.0:  72 new features, 62 bug fixes

You can get these numbers programmatically:

R4 <- news()
table(R4$Category)

R3 <- news(package = "R-3")
table(R3$Version, R3$Category)

Duncan Murdoch

______________________________________________
[hidden email] mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Reply | Threaded
Open this post in threaded view
|

Re: edit() doubles backslashes when keep.source=TRUE

Dirk Eddelbuettel
In reply to this post by Martin Maechler

On 15 May 2020 at 15:41, Martin Maechler wrote:
| <whining>
|
|     Why does nobody anymore  help R development by working with
|     "R-devel", or at least then the alpha, beta and the "RC"
|     (Release Candidate) versions that we release daily for about one
|     month before the final release?
|
|     Notably a highly staffed enterprise such as Rstudio (viz the bug
|     report 17800 above), but also others could really help by
|     starting to use the "next version" of R on a routine basis ...
|
| <whining/>

Seconded. Without testing we can never know. R Core does their part.

I provided weekly Debian binaries. One each for the two alphas releases, for
the beta release, for the release candidate.  It is easy to use these, for
example in a Docker container.

It is also easy to use this on a normal machine as they are standard (Debian)
packages: install, try some tests, uninstall, revert to previous version by
installing that.

Dirk

--
http://dirk.eddelbuettel.com | @eddelbuettel | [hidden email]

______________________________________________
[hidden email] mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Reply | Threaded
Open this post in threaded view
|

Re: edit() doubles backslashes when keep.source=TRUE

R devel mailing list

> On Friday, May 15, 2020, 12:13:04 PM EDT, Dirk Eddelbuettel <[hidden email]> wrote:
> On 15 May 2020 at 15:41, Martin Maechler wrote:
> | <whining>
> |
> |    Why does nobody anymore  help R development by working with
> |    "R-devel", or at least then the alpha, beta and the "RC"
> |    (Release Candidate) versions that we release daily for about one
> |    month before the final release?
> |
> |    Notably a highly staffed enterprise such as Rstudio (viz the bug
> |    report 17800 above), but also others could really help by
> |    starting to use the "next version" of R on a routine basis ...
> |
> | <whining/>
>
> Seconded. Without testing we can never know. R Core does their part.
>
> I provided weekly Debian binaries. One each for the two alphas releases, for
> the beta release, for the release candidate.  It is easy to use these, for
> example in a Docker container.
>
> It is also easy to use this on a normal machine as they are standard (Debian)
> packages: install, try some tests, uninstall, revert to previous version by
> installing that.
>
> Dirk

This is a very reasonably request, and all useRs who benefit from the
tireless work of R-core should consider doing it.  I have considered
it, but compiling R from sources on OS X has been my stumbling block.
At least last time I tried I got stuck at the  Fortran step. It doesn't
 help I have very limited experience compiling  software of the complexity
of R.  Really, I've only done it within the warm welcoming confines of the
 vagrant image Tomas Kalibera set up for `rchk`.

I also use r-devel on docker, but that isn't very practical for
day-to-day usage, which is what I think we need.

What would it take to generate pre-release binaries for OS X (and Windows)?  I
imagine if such were available the volume of testers would increase
dramatically (at least, I haven't seen them if they exist). 
Maybe something the R Consortium would consider funding?

Best,

B.

______________________________________________
[hidden email] mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Reply | Threaded
Open this post in threaded view
|

Re: edit() doubles backslashes when keep.source=TRUE

Bemis, Kylie
Nightly binary builds of R-devel for macOS are available: http://mac.r-project.org

~~~
Kylie Ariel Bemis (she/her)
Khoury College of Computer Sciences
Northeastern University
kuwisdelu.github.io<https://kuwisdelu.github.io>










On May 15, 2020, at 12:48 PM, brodie gaslam via R-devel <[hidden email]<mailto:[hidden email]>> wrote:


On Friday, May 15, 2020, 12:13:04 PM EDT, Dirk Eddelbuettel <[hidden email]<mailto:[hidden email]>> wrote:
On 15 May 2020 at 15:41, Martin Maechler wrote:
| <whining>
|
|    Why does nobody anymore  help R development by working with
|    "R-devel", or at least then the alpha, beta and the "RC"
|    (Release Candidate) versions that we release daily for about one
|    month before the final release?
|
|    Notably a highly staffed enterprise such as Rstudio (viz the bug
|    report 17800 above), but also others could really help by
|    starting to use the "next version" of R on a routine basis ...
|
| <whining/>

Seconded. Without testing we can never know. R Core does their part.

I provided weekly Debian binaries. One each for the two alphas releases, for
the beta release, for the release candidate.  It is easy to use these, for
example in a Docker container.

It is also easy to use this on a normal machine as they are standard (Debian)
packages: install, try some tests, uninstall, revert to previous version by
installing that.

Dirk

This is a very reasonably request, and all useRs who benefit from the
tireless work of R-core should consider doing it.  I have considered
it, but compiling R from sources on OS X has been my stumbling block.
At least last time I tried I got stuck at the  Fortran step. It doesn't
help I have very limited experience compiling  software of the complexity
of R.  Really, I've only done it within the warm welcoming confines of the
vagrant image Tomas Kalibera set up for `rchk`.

I also use r-devel on docker, but that isn't very practical for
day-to-day usage, which is what I think we need.

What would it take to generate pre-release binaries for OS X (and Windows)?  I
imagine if such were available the volume of testers would increase
dramatically (at least, I haven't seen them if they exist).
Maybe something the R Consortium would consider funding?

Best,

B.

______________________________________________
[hidden email]<mailto:[hidden email]> mailing list
https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstat.ethz.ch%2Fmailman%2Flistinfo%2Fr-devel&amp;data=02%7C01%7Ck.bemis%40northeastern.edu%7C66883f8d39094f87847608d7f8efd23e%7Ca8eec281aaa34daeac9b9a398b9215e7%7C0%7C0%7C637251581223782724&amp;sdata=cVYbvv%2B2fqwKpMUCM6iBGu4wLOLQvQUwv4SOapZf5mM%3D&amp;reserved=0


        [[alternative HTML version deleted]]

______________________________________________
[hidden email] mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Reply | Threaded
Open this post in threaded view
|

Re: edit() doubles backslashes when keep.source=TRUE

Avraham Adler
In reply to this post by R devel mailing list
I build windows binaries from source. As of now, the only choice is R-revel
unless I want to monkey around more with Jeroens’s PKGBUILD script (which
is On my to-do list).

It’s pretty straightforward, although I’m seeing a lot of issues with
packages which had explicit calls to LOCALSOFT in configure.win as that
doesn’t exist anymore.

The binaries have passed make check, though. Would it help if I built some
and forwarded it somewhere?

Avi

On Fri, May 15, 2020 at 12:48 PM brodie gaslam via R-devel <
[hidden email]> wrote:

>
> > On Friday, May 15, 2020, 12:13:04 PM EDT, Dirk Eddelbuettel <
> [hidden email]> wrote:
> > On 15 May 2020 at 15:41, Martin Maechler wrote:
> > | <whining>
> > |
> > |    Why does nobody anymore  help R development by working with
> > |    "R-devel", or at least then the alpha, beta and the "RC"
> > |    (Release Candidate) versions that we release daily for about one
> > |    month before the final release?
> > |
> > |    Notably a highly staffed enterprise such as Rstudio (viz the bug
> > |    report 17800 above), but also others could really help by
> > |    starting to use the "next version" of R on a routine basis ...
> > |
> > | <whining/>
> >
> > Seconded. Without testing we can never know. R Core does their part.
> >
> > I provided weekly Debian binaries. One each for the two alphas releases,
> for
> > the beta release, for the release candidate.  It is easy to use these,
> for
> > example in a Docker container.
> >
> > It is also easy to use this on a normal machine as they are standard
> (Debian)
> > packages: install, try some tests, uninstall, revert to previous version
> by
> > installing that.
> >
> > Dirk
>
> This is a very reasonably request, and all useRs who benefit from the
> tireless work of R-core should consider doing it.  I have considered
> it, but compiling R from sources on OS X has been my stumbling block.
> At least last time I tried I got stuck at the  Fortran step. It doesn't
>  help I have very limited experience compiling  software of the complexity
> of R.  Really, I've only done it within the warm welcoming confines of the
>  vagrant image Tomas Kalibera set up for `rchk`.
>
> I also use r-devel on docker, but that isn't very practical for
> day-to-day usage, which is what I think we need.
>
> What would it take to generate pre-release binaries for OS X (and
> Windows)?  I
> imagine if such were available the volume of testers would increase
> dramatically (at least, I haven't seen them if they exist).
> Maybe something the R Consortium would consider funding?
>
> Best,
>
> B.
>
> ______________________________________________
> [hidden email] mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
>
--
Sent from Gmail Mobile

        [[alternative HTML version deleted]]

______________________________________________
[hidden email] mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Reply | Threaded
Open this post in threaded view
|

Re: edit() doubles backslashes when keep.source=TRUE

Peter Dalgaard-2
In reply to this post by R devel mailing list
Actually, it's not that hard to set up for a source compile for MacOS. The hard part is to do it precisely like the CRAN binaries so that you can run binary packages off CRAN, but in other setups you can just build packages from source.

A stone in the shoe has been that the documentation on mac.r-project.org was littered with out-of-date information, but it seems that Simon has now cleaned this up considerably. It should now be possible simply to follow instructions on http://mac.r-project.org/tools/. I'm sure Simon will be receptive to information if something doesn't quite work.

-pd

> On 15 May 2020, at 18:48 , brodie gaslam via R-devel <[hidden email]> wrote:
>
>>
>> On Friday, May 15, 2020, 12:13:04 PM EDT, Dirk Eddelbuettel <[hidden email]> wrote:
>> On 15 May 2020 at 15:41, Martin Maechler wrote:
>> | <whining>
>> |
>> |    Why does nobody anymore  help R development by working with
>> |    "R-devel", or at least then the alpha, beta and the "RC"
>> |    (Release Candidate) versions that we release daily for about one
>> |    month before the final release?
>> |
>> |    Notably a highly staffed enterprise such as Rstudio (viz the bug
>> |    report 17800 above), but also others could really help by
>> |    starting to use the "next version" of R on a routine basis ...
>> |
>> | <whining/>
>>
>> Seconded. Without testing we can never know. R Core does their part.
>>
>> I provided weekly Debian binaries. One each for the two alphas releases, for
>> the beta release, for the release candidate.  It is easy to use these, for
>> example in a Docker container.
>>
>> It is also easy to use this on a normal machine as they are standard (Debian)
>> packages: install, try some tests, uninstall, revert to previous version by
>> installing that.
>>
>> Dirk
>
> This is a very reasonably request, and all useRs who benefit from the
> tireless work of R-core should consider doing it.  I have considered
> it, but compiling R from sources on OS X has been my stumbling block.
> At least last time I tried I got stuck at the  Fortran step. It doesn't
> help I have very limited experience compiling  software of the complexity
> of R.  Really, I've only done it within the warm welcoming confines of the
> vagrant image Tomas Kalibera set up for `rchk`.
>
> I also use r-devel on docker, but that isn't very practical for
> day-to-day usage, which is what I think we need.
>
> What would it take to generate pre-release binaries for OS X (and Windows)?  I
> imagine if such were available the volume of testers would increase
> dramatically (at least, I haven't seen them if they exist).  
> Maybe something the R Consortium would consider funding?
>
> Best,
>
> B.
>
> ______________________________________________
> [hidden email] mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel

--
Peter Dalgaard, Professor,
Center for Statistics, Copenhagen Business School
Solbjerg Plads 3, 2000 Frederiksberg, Denmark
Phone: (+45)38153501
Office: A 4.23
Email: [hidden email]  Priv: [hidden email]

______________________________________________
[hidden email] mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Reply | Threaded
Open this post in threaded view
|

Re: edit() doubles backslashes when keep.source=TRUE

Peter Dalgaard-2
To discuss this further, we should probably move over to R-sig-mac and change the subject header.

-pd

> On 15 May 2020, at 19:26 , peter dalgaard <[hidden email]> wrote:
>
> Actually, it's not that hard to set up for a source compile for MacOS.....

--
Peter Dalgaard, Professor,
Center for Statistics, Copenhagen Business School
Solbjerg Plads 3, 2000 Frederiksberg, Denmark
Phone: (+45)38153501
Office: A 4.23
Email: [hidden email]  Priv: [hidden email]

______________________________________________
[hidden email] mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Reply | Threaded
Open this post in threaded view
|

Re: Testing before release (was: edit() doubles backslashes when keep.source=TRUE)

Abby Spurdle
In reply to this post by Duncan Murdoch-2
This perhaps diverges from the intent of the thread, but...

I wanted to say I'm extremely grateful to the people who go the
through the bug reports.
It's an extremely important job (in the long run, particularly), but
perhaps not quite as "sexy"-sounding as other roles, and probably
under-valued.

So, thank you to the bug-fixers...

:)

On Sat, May 16, 2020 at 2:54 AM Duncan Murdoch <[hidden email]> wrote:

>
> On 15/05/2020 9:41 a.m., Martin Maechler wrote:
> [ deletions ]
> > <whining>
> >
> >      Why does nobody anymore  help R development by working with
> >      "R-devel", or at least then the alpha, beta and the "RC"
> >      (Release Candidate) versions that we release daily for about one
> >      month before the final release?
> >
> >      Notably a highly staffed enterprise such as Rstudio (viz the bug
> >      report 17800 above), but also others could really help by
> >      starting to use the "next version" of R on a routine basis ...
> >
> > <whining/
> I understand the whining, bugs that get released are embarrassing.  But
> when I read the NEWS, I can see that both the NEW FEATURES and BUG FIXES
> sections of x.y.0 releases tend to be much longer than the BUG FIXES
> sections in patch releases.  That seems to indicate that things are
> working reasonably well.
>
> For a really rough measure, just counting bullet points:
>
> R 4.0.0:  65 new features, 55 bug fixes
>
> R 3.6.3:  1 new feature, 7 bug fixes
>
> R 3.6.2:  2 new features, 21 bug fixes
>
> R 3.6.1:  0 new features, 16 bug fixes
>
> R 3.6.0:  72 new features, 62 bug fixes
>
> You can get these numbers programmatically:
>
> R4 <- news()
> table(R4$Category)
>
> R3 <- news(package = "R-3")
> table(R3$Version, R3$Category)
>
> Duncan Murdoch
>
> ______________________________________________
> [hidden email] mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel

______________________________________________
[hidden email] mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Reply | Threaded
Open this post in threaded view
|

Re: [External] Re: Testing before release (was: edit() doubles backslashes when keep.source=TRUE)

luke-tierney
On Fri, 15 May 2020, Abby Spurdle wrote:

> This perhaps diverges from the intent of the thread, but...
>
> I wanted to say I'm extremely grateful to the people who go the
> through the bug reports.
> It's an extremely important job (in the long run, particularly), but
> perhaps not quite as "sexy"-sounding as other roles, and probably
> under-valued.
>
> So, thank you to the bug-fixers...

Yes: Thank You!!

Best,

luke

>
> :)
>
> On Sat, May 16, 2020 at 2:54 AM Duncan Murdoch <[hidden email]> wrote:
>>
>> On 15/05/2020 9:41 a.m., Martin Maechler wrote:
>> [ deletions ]
>>> <whining>
>>>
>>>      Why does nobody anymore  help R development by working with
>>>      "R-devel", or at least then the alpha, beta and the "RC"
>>>      (Release Candidate) versions that we release daily for about one
>>>      month before the final release?
>>>
>>>      Notably a highly staffed enterprise such as Rstudio (viz the bug
>>>      report 17800 above), but also others could really help by
>>>      starting to use the "next version" of R on a routine basis ...
>>>
>>> <whining/
>> I understand the whining, bugs that get released are embarrassing.  But
>> when I read the NEWS, I can see that both the NEW FEATURES and BUG FIXES
>> sections of x.y.0 releases tend to be much longer than the BUG FIXES
>> sections in patch releases.  That seems to indicate that things are
>> working reasonably well.
>>
>> For a really rough measure, just counting bullet points:
>>
>> R 4.0.0:  65 new features, 55 bug fixes
>>
>> R 3.6.3:  1 new feature, 7 bug fixes
>>
>> R 3.6.2:  2 new features, 21 bug fixes
>>
>> R 3.6.1:  0 new features, 16 bug fixes
>>
>> R 3.6.0:  72 new features, 62 bug fixes
>>
>> You can get these numbers programmatically:
>>
>> R4 <- news()
>> table(R4$Category)
>>
>> R3 <- news(package = "R-3")
>> table(R3$Version, R3$Category)
>>
>> Duncan Murdoch
>>
>> ______________________________________________
>> [hidden email] mailing list
>> https://stat.ethz.ch/mailman/listinfo/r-devel
>
> ______________________________________________
> [hidden email] mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
>

--
Luke Tierney
Ralph E. Wareham Professor of Mathematical Sciences
University of Iowa                  Phone:             319-335-3386
Department of Statistics and        Fax:               319-335-3017
    Actuarial Science
241 Schaeffer Hall                  email:   [hidden email]
Iowa City, IA 52242                 WWW:  http://www.stat.uiowa.edu

______________________________________________
[hidden email] mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Reply | Threaded
Open this post in threaded view
|

Re: edit() doubles backslashes when keep.source=TRUE

Tomas Kalibera
In reply to this post by R devel mailing list
Thanks for reporting this, it is a bug, now fixed in R-devel and
R-patched (PR#17800).

Best
Tomas

On 5/15/20 3:50 AM, William Dunlap via R-devel wrote:

> Is it just my installation or does edit() (or fix(), etc.) in R-4.0.0
> double all the backslashes when options(keep.source=TRUE)?  E.g.,
>
>> options(keep.source=TRUE)
>> f <- function(x) { cat("\t", x, "\n", sep="") }
>> edit(f) # exit the editor without making any changes
> The editor (vi or notepad) shows doubled backslashes
>      function(x) { cat("\\t", x, "\\n", sep="") }
> as does the return value of edit().
>
> If I set options(keep.source=FALSE) before defining 'f' or remove t's
> 'srcref' attribute then the backslashes are left alone.
>
> Bill Dunlap
> TIBCO Software
> wdunlap tibco.com
>
> [[alternative HTML version deleted]]
>
> ______________________________________________
> [hidden email] mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel

______________________________________________
[hidden email] mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel