[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

.octave_hist content

From: CdeMills
Subject: .octave_hist content
Date: Tue, 11 Jan 2011 01:57:17 -0800 (PST)


I found myself regularly trapped into the following problem: while debugging
some piece of code, I repeat some operation sequence again and again and
again. At some point, the .octave_hist is totally saturated with those
statements, and the info about the context where the debugging code was
tested is lost.

Would it be possible, for the history file, to store:
- statement last execution time
- statement value

This way, something repeated a big number of times would only 'consume' one
line in the history file. Storing for each statement an last execution time
will permit to purge the history from commands unused since three months,
f.i. A statement is a repeat of a previous one iff there are equal using
strcmp. Would it be a big deal to implement such mechanism ?



View this message in context:
Sent from the Octave - General mailing list archive at

reply via email to

[Prev in Thread] Current Thread [Next in Thread]