> Re: todo.py is not referenced in any *.leo file from plugins/
> Is this ok?
No, that was my mistake, I create them in leoPlugins.leo (i.e. the
editing copy bzr ignores) and then forget to move them over. I'll add
it right away.
Cheers -Terry
> Re: todo.py is not referenced in any *.leo file from plugins/
.py files in .../plugins referred to by no @thin nodes:
(*** three of them are mine, although I think at least one of those is
referenced by @shadow rather than @thin, I'll fix these now)
backlink.py ***
dyna_menu.py
dynacommon.py
exampleTemacsExtension.py
graphcanvas.py ***
gtkDialogs.py
gtkGui.py
initinclass.py
leo_interface.py
leo_pdf.py
mod_leo2ascd.py
override_commands.py
qt_main.py
qt_quicksearch.py
rst.py
rst2.py
scrolledmessage.py
searchbar.py
temacs.py
threading_colorizer.py
todo.py ***
usetemacs.py
zenity_file_dialogs.py
> (*** three of them are mine, although I think at least one of those is
> referenced by @shadow rather than @thin, I'll fix these now)
graphcanvas and backlinks.py are referenced by @shadow nodes, I'll
leave them that way unless Edward objects.
todo.py is added at r1666
Adding the @thin node was, as usual, fiddly. I tried @auto import, but
turns out I'd used @thin rather than @shadow in leoPlugins.leo, so that
didn't work. I'd already deleted leoPlugins.leo, so copy and paste was
out.
The empty @auto node I created and saved before reverting to trigger
the import very politely declined to trash the existing .py file,
good. The empty @thin node I used in the same way had no such qualms
and deleted todo.py, even though the node was empty and without
children. No problem, bzr revert todo.py and move the @thin in @thin
node that results up one level, but not a good process for the novice.
Cheers -Terry