And to answer my own question... On Wed, Apr 20, 2016 at 10:47:46PM +0200, Alistair Grant wrote: > Hi Stepharo, > > Thanks very much for your feedback. > ... > > So, time to learn more about Monticello... Reading the Updated PbE is > helpful, however I did notice one thing which doesn't match my > experience. On page 150 it is discussing how you can't lose code... > > "This is because all of the code that you executed is saved in the > .changes file. All of it! This includes one liners that you evaluate in > a workspace, as well as code that you add to a class while programming." > > Should "workspace" be changed to "playground"? > > My experience has been that code evaluated in the playground is *not* > saved to the changes file (Pharo 4.0 and 5.0). Is there a way to tell > Pharo to save evaluated code to the changes file? (I admit to being > lazy and not trying to figure this one out myself yet).
It looks like evaluated code is saved in the play-cache directory and accessible through the Spotter. Perhaps you could change the paragraph to something like: This is because all of the code that you write is saved in the .changes file, and expressions that are evaluated in the playground are saved to the play-cache. Expressions from the playground may be found using the spotter as described in section 2.11. (And then go on to describe how to recover code) Thanks, Alistair
