This blog is updated daily.
A general description is here.
‘R CMD Sweave’ and ‘R CMD Stangle’ did not run.
The fix for PR#14583 caused inconsistent behaviour in other areas, e.g.
PR#14628, extra lines appearing in image displays, and uneven bases on
histograms PR#14632.
Opening large numbers of ‘windows()’ graphics devices could cause some
of them to fail to redraw (PR#14668).
‘R CMD Sweave’ and ‘R CMD Stangle’ did not run.
The fix for PR#14583 caused inconsistent behaviour in other areas, e.g. PR#14628, extra lines appearing in image displays, and uneven bases on histograms PR#14632.
Opening large numbers of ‘windows()’ graphics devices could cause some of them to fail to redraw (PR#14668).
Opening large numbers of ‘windows()’ graphics devices could cause some of them to fail to redraw (PR#14668).
The fix for PR#14583 caused inconsistent behaviour in other areas, e.g. PR#14628, extra lines appearing in image displays, and uneven bases on histograms PR#14632.
‘R CMD Sweave’ and ‘R CMD Stangle’ did not run.
The windows() screen device would sometimes fail to plot (visibly) points with ‘pch="."’. PR#14583
Shutting down the R session cleaned up the temporary directory before closing all graphics devices. On Windows this necessitated changing the working directory, so some devices (e.g. ‘tiff()’) could write files in the wrong directory if closed during shutdown. The order has been reversed.
‘R CMD build’ no longer attempts to preserve file permissions on
Windows, because Windows (unlike POSIX-compliant OSes) stops read-only
files being deleted in version-control directories.
‘shell.exec()’ now interprets files relative to the current working
directory (rather than ‘R_HOME’).
‘file.info()’ now accepts ‘file’ names with trailing directory
separators, even though such names are invalid on Windows.
The ‘windows()’ family of devices now supports() per-pixel alpha for
raster images.
Launching the PDF manuals from the Rgui menus did not work on some
versions of Windows.
The windows() screen device would sometimes fail to plot points with
‘pch="."’. PR#14583
‘system()’ and related functions sometimes failed when run in ‘Rgui’.
Saving to PDF from the menu of a ‘windows()’ device used defaults for
‘family’, ‘fg’ and ‘bg’ from ‘ps.options()’ rather than ‘pdf.options()’
(but the factory-fresh defaults were the same).
Shutting down the R session cleaned up the temporary directory before
closing all graphics devices. On Windows this necessitated changing
the working directory, so some devices (e.g. ‘tiff()’) could write
files in the wrong directory in closed during shutdown. The order has
been reversed.
‘R CMD build’ no longer attempts to preserve file permissions on Windows, because Windows (unlike POSIX-compliant OSes) stops read-only files being deleted in version-control directories.
‘shell.exec()’ now interprets files relative to the current working directory (rather than ‘R_HOME’).
‘file.info()’ now accepts ‘file’ names with trailing directory separators, even though such names are invalid on Windows.
The ‘windows()’ family of devices now supports() per-pixel alpha for raster images.
Launching the PDF manuals from the Rgui menus did not work on some versions of Windows.
The windows() screen device would sometimes fail to plot points with ‘pch="."’. PR#14583
‘system()’ and related functions sometimes failed when run in ‘Rgui’.
Saving to PDF from the menu of a ‘windows()’ device used defaults for ‘family’, ‘fg’ and ‘bg’ from ‘ps.options()’ rather than ‘pdf.options()’ (but the factory-fresh defaults were the same).
Shutting down the R session cleaned up the temporary directory before closing all graphics devices. On Windows this necessitated changing the working directory, so some devices (e.g. ‘tiff()’) could write files in the wrong directory in closed during shutdown. The order has been reversed.
Saving to PDF from the menu of a ‘windows()’ device used defaults for
‘family’, ‘fg’ and ‘bg’ from ‘ps.options()’ rather than ‘pdf.options()’
(but the factory-fresh defaults were the same).
Shutting down the R session cleaned up the temporary directory before
closing all graphics devices. On Windows this necessitated changing
the working directory, so some devices (e.g. ‘tiff()’) could write
files in the wrong directory. The order has been reversed.
Saving to PDF from the menu of a ‘windows()’ device used defaults for ‘family’, ‘fg’ and ‘bg’ from ‘ps.options()’ rather than ‘pdf.options()’ (but the factory-fresh defaults were the same).
Shutting down the R session cleaned up the temporary directory before closing all graphics devices. On Windows this necessitated changing the working directory, so some devices (e.g. ‘tiff()’) could write files in the wrong directory in closed during shutdown. The order has been reversed.
‘system()’ and related functions sometimes failed when run in ‘Rgui’.
The windows() screen device would sometimes fail to plot points with ‘pch="."’. PR#14583
The ‘windows()’ family of devices now supports() per-pixel alpha for raster images.
Shutting down the R session cleaned up the temporary directory before closing all graphics devices. On Windows this necessitated changing the working directory, so some devices (e.g. ‘tiff()’) could write files in the wrong directory. The order has been reversed.
‘file.info()’ now accepts ‘file’ names with trailing directory separators, even though such names are invalid on Windows.
‘file.info()’ now accepts ‘file’ names with trailing directory separators.
‘file.info()’ now accepts ‘file’ names with trailing directory separators: those are not valid on Windows but R has some ignorant users.
Saving to PDF from the menu of a ‘windows()’ device used defaults for ‘family’, ‘fg’ and ‘bg’ from ‘ps.options()’ rather than ‘pdf.options()’ (but the factory-fresh defaults were the same).
‘R CMD build’ no longer attempts to preserve file permissions on Windows, because Windows (unlike POSIX-compliant OSes) stops read-only files being deleted in version-control directories.
‘shell.exec()’ now interprets files relative to the current working directory (rather than ‘R_HOME’).
‘R CMD build’ no longer attempts to preserve file permissions on Windows, because Windows (unlike POSIX-complant OSes) stops read-only files being deleted in version-control directories.
‘shell.exec()’ now interprets files relative to the current working directory.
Launching the PDF manuals from the Rgui menus did not work on some versions of Windows.
The sources now work with ‘libpng-1.5.1’, ‘jpegsrc.v8c’ (which are used in the CRAN builds) and ‘tiff-4.0.0beta6’ (CRAN builds use 3.9.1). It is possible that they no longer work with older versions than ‘libpng-1.4.5’.
‘Rgui’ has a new menu item for the PDF ‘Sweave User Manual’.
The sources now work with ‘libpng-1.5.1’, ‘ jpegsrc.v8c’ (which are used in the CRAN builds) and ‘tiff-4.0.0beta6’ (CRAN builds use 3.9.1). It is possible that they no longer work with older versions than ‘libpng-1.4.5’.
Printing extremely long string values could overflow the stack and cause the GUI to crash. (PR#14543)
The environment variable ‘R_HOME’ in an R session now uses slash as the path separator (as it always has when set by ‘Rcmd.exe’).