Prof Brian Ripley wrote:
Yes, it is by design, and not R's design at that.
How (or if) the history is saved is determined by the GUI interface in
use. In this case it appears to be command-line R built with readline
support, in which case the saving is done by readline's write_history.
And
Yes, it is by design, and not R's design at that.
How (or if) the history is saved is determined by the GUI interface in
use. In this case it appears to be command-line R built with readline
support, in which case the saving is done by readline's write_history.
And although the history.info
Hi,
This is with a centos 5.3 x86_64 system, using R 2.8.1 (details below).
In a directory where R is invoked, at the end of a session R offers to
Save workspace image. Replying yes creates/updates at least two files
in the current directory: .Rhistory and .RData.
.Rhistory is created with
nicolas.thierry-m...@imag.fr wrote:
Hi,
This is with a centos 5.3 x86_64 system, using R 2.8.1 (details below).
In a directory where R is invoked, at the end of a session R offers to
Save workspace image. Replying yes creates/updates at least two files
in the current directory: .Rhistory
