I'm not an expert on nav_qt.py. I'm not an expert on Leo-Editor. I'm
working on a plugin to navigate the position visited list.
Consequently, I've noticed a possible problem.
The position visited list grows without bound. This list is attribute
beadlist of the instance of class NodeHistory.
If you navigate with arrow keys, node history grows with each move. So you
should at least have 100 entries in node history.
SegundoBob bhoss...@ieee.org wrote:
I'm not an expert on nav_qt.py. I'm not an expert on Leo-Editor. I'm
working on a plugin to navigate the position visited list.
On Fri, Jul 29, 2011 at 11:20 AM, SegundoBob bhoss...@ieee.org wrote:
Until recently, the position-visited-list was truncated by add-new-
position-to-list (method update()) to the current position (i.e.,
beadPointer) whenever the next or previous buttons had been used
to navigate to a
On Jul 29, 10:59 am, Edward K. Ream edream...@gmail.com wrote:
Because of unlimited undo, *nothing* (that is, no data) is *ever*
deleted while Leo is running. You could call this a *large* memory
leak.
I missed that (and still can't find where) undo uses the position
visited list. I withdrew
