similar to: nc file

El lun., 30 oct. 2023 12:26, Roger Bivand <Roger.Bivand at nhh.no> escribi?: > I also noticed this: > > https://www.theregister.com/2023/10/13/gnome_proposes_dropping_x11/ > > which is concerning. Until now, I've retained X11 on Fedora because of > difficulties in screen sharing via zoom in Wayland sessions. > KDE Plasma user here. FWIW, I've been using Wayland

I also noticed this: https://www.theregister.com/2023/10/13/gnome_proposes_dropping_x11/ which is concerning. Until now, I've retained X11 on Fedora because of difficulties in screen sharing via zoom in Wayland sessions. Roger -- Roger Bivand Emeritus Professor Norwegian School of Economics Postboks 3490 Ytre Sandviken, 5045 Bergen, Norway Roger.Bivand at nhh.no

The legacy R spatial infrastructure packages maptools, rgdal and rgeos will be archived by CRAN on Monday, October 16, 2023; rgrass7 has already been replaced by rgrass and will be archived with the retiring packages. The choice of date matches the previously announced archiving during October 2023, and the specific date matches the release schedule of Bioconductor 3.18 (some Bioconductor

The legacy R spatial infrastructure packages maptools, rgdal and rgeos will be archived by CRAN on Monday, October 16, 2023; rgrass7 has already been replaced by rgrass and will be archived with the retiring packages. The choice of date matches the previously announced archiving during October 2023, and the specific date matches the release schedule of Bioconductor 3.18 (some Bioconductor

The third report on the R-spatial evolution project has been published. https://r-spatial.org/r/2023/04/10/evolution3.html It links back to earlier blogs and presentations, and focuses on work that maintainers of R packages and workflows using rgdal, rgeos and maptools need to put in train now before the packages are archived on CRAN. The first changes will occur in June 2023, and the

The third report on the R-spatial evolution project has been published. https://r-spatial.org/r/2023/04/10/evolution3.html It links back to earlier blogs and presentations, and focuses on work that maintainers of R packages and workflows using rgdal, rgeos and maptools need to put in train now before the packages are archived on CRAN. The first changes will occur in June 2023, and the

A new version of the sp package, 2.0-0, has been published on CRAN. This new version defaults to using the sf package rather than the rgdal package, and deprecates use of the rgeos package. These changes are described in https://r-spatial.org/r/2023/05/15/evolution4.html, and lead up to the planned archiving of the retiring packages: maptools, rgdal and rgeos in October 2023. This version issues

A new version of the sp package, 2.0-0, has been published on CRAN. This new version defaults to using the sf package rather than the rgdal package, and deprecates use of the rgeos package. These changes are described in https://r-spatial.org/r/2023/05/15/evolution4.html, and lead up to the planned archiving of the retiring packages: maptools, rgdal and rgeos in October 2023. This version issues

The rgeoda package, version 0.0.10-4, is, as mentioned in this thread, available from https://geodacenter.r-universe.dev/rgeoda, pending the release of an updated version of the BH package with corrected Boost C++ headers that do not fail on forthcoming clang++ 19, see https://github.com/GeoDaCenter/rgeoda/issues/49. A source version of rgeoda 0.0.10-7 is archived on

On Sat, 10 Nov 2018, Andreas Storvik Strauman wrote: > Hello! I'm confused as to what the actual problem with includeRnw is? Is > the problem that it relies on R-knitr? Before it would be withdrawn, may > I be given an opportunity to fix said problem? Yes, the problem is that it expesses an external dependence on anything outside texlive. On packaging systems (for me Fedora),

Hello! I'm confused as to what the actual problem with includeRnw is? Is the problem that it relies on R-knitr? Before it would be withdrawn, may I be given an opportunity to fix said problem? includeRnw only invokes the already existing R installation, and should not affect any other global settings or affect the installation in any way. If this is the case, it's a bug and I'd

We're happy to announce the CRAN release of "sp", an R package which has new-style classes and methods for spatial data, version 0.7-9. Spatial data types that sp implements are: points, grids, lines, and polygons (i.e., rings) optionally with holes. Methods include + the usual print, summary, plot, [, [[, $, ... + coercion between types (e.g. points and grids, matrices,

We're happy to announce the CRAN release of "sp", an R package which has new-style classes and methods for spatial data, version 0.7-9. Spatial data types that sp implements are: points, grids, lines, and polygons (i.e., rings) optionally with holes. Methods include + the usual print, summary, plot, [, [[, $, ... + coercion between types (e.g. points and grids, matrices,

On Sat, 10 Nov 2018 at 15:17, Roger Bivand <Roger.Bivand at nhh.no> wrote: > > On upgrading my F28 to F29, I've found that R-core and a number of R > packages: > > R-evaluate R-glue R-highr R-knitr R-magrittr R-markdown R-mime R-stringi > R-stringr R-yaml > > are installed, although I only ever install R from source and always keep > my Rs locally. So I

Thanks to Roger Bivand, my problem was solved. binutils 2.14 was updatet to binutils 2.15, as indicated under. Geir Helge Systad Norwegian Institute for Nature Research Arctic Ecology, Polarmilj??senteret, N-9296 Troms??, Norway Adress aug-04 to feb-05: Albert Pettersonsvei 13, N-5750 Odda fax +47 85 03 82 14 phone +47 53 64 24 94 mobil +47 91 63 70 55 E-mail: geir.systad at nina.no

A new release of rgdal, a package providing bindings for the Geospatial Data Abstraction Library for reading and writing spatial data, has reached CRAN. This release changes the error handling mechanisms, and is more fully described in a posting on R-sig-geo: https://stat.ethz.ch/pipermail/r-sig-geo/2011-July/012126.html If any users observe unexpected behaviour following update, please

A new release of rgdal, a package providing bindings for the Geospatial Data Abstraction Library for reading and writing spatial data, has reached CRAN. This release changes the error handling mechanisms, and is more fully described in a posting on R-sig-geo: https://stat.ethz.ch/pipermail/r-sig-geo/2011-July/012126.html If any users observe unexpected behaviour following update, please

Dear All I would really appreciate some help with a script which a colleague wrote for me, but I am having problems running (and have not been able to contact my colleague). The script is designed to compare the area of suitable habitat in binary projections of a large number of species current and future distributions, and create an excel file detailing the total area suitable in the

Release of revised version of R/GRASS GIS raster and sites data interface. The latest version of the R contributed package "GRASS", release 0.1-6, may be downloaded from CRAN (cran.r-project.org) - contributed packaged section, "Devel" directory, file: GRASS_0.1-6.tar.gz. It may also be downloaded from ftp://reclus.nhh.no/pub/R/GRASS_0.1-6.tar.gz. This version is intended for

On Sat, 10 Nov 2018, I?aki Ucar wrote: > On Sat, 10 Nov 2018 at 15:17, Roger Bivand <Roger.Bivand at nhh.no> wrote: >> >> On upgrading my F28 to F29, I've found that R-core and a number of R >> packages: >> >> R-evaluate R-glue R-highr R-knitr R-magrittr R-markdown R-mime R-stringi >> R-stringr R-yaml >> >> are installed, although I