[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Manipulating history in iniitialization files
From: |
Rafael Laboissiere |
Subject: |
Manipulating history in iniitialization files |
Date: |
Wed, 9 Mar 2011 23:24:28 +0100 |
User-agent: |
Mutt/1.5.20 (2009-06-14) |
Dear Octave maintainers,
First of all, thanks for your continuing effort in developing Octave. I
really appreciate it and I regret not having time to maintain the
Octave-related Debian packages anymore.
My question/request today regards the code in src/octave.cc, where I read
the following:
execute_startup_files ();
initialize_history (read_history_file);
Is there a strong reason for the order of execution above? If it was
reversed:
initialize_history (read_history_file);
execute_startup_files ();
then the history could be manipulated in startup files, like adding
timestamps or the like. I have not investigated the possible side
effects of this reversal, though, but it could be a beneficial change.
Cheers,
Rafael Laboissiere
- Manipulating history in iniitialization files,
Rafael Laboissiere <=