[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: saving Octave state?
From: |
John W. Eaton |
Subject: |
Re: saving Octave state? |
Date: |
Tue, 30 Nov 2010 15:14:58 -0500 |
On 30-Nov-2010, Mike Miller wrote:
| I decided to mimic the R filenames and call the data and history files
| .OData and .Ohistory (instead of .RData and .Rhistory). This is in my
| ~/.octaverc file:
|
|
| history_file (".Ohistory");
| if ( exist(".OData", "file") == 2 )
| load(".OData") ;
| endif
|
|
| So it automatically loads history and data, if they are present. I'm not
| sure if any aspect of the state of the previous instance of Octave would
| be missed when I launch Octave in the same directory if I had done this
| just before quitting the previous time:
|
| save .OData
|
| What do you think?
Use a function to do this with atexit if you want to ensure that this
happens every time Octave quits.
The only thing I can think of that you are not saving is the internal
state managed by functions like more, octave_core_file_name,
output_precision, etc. If you have changed any of these from their
defaults, that info will not be saved and restored automatically.
jwe