On my quest for a list of recently edited nodes, I realized I'm asking for "mtime", as in $ stat file <snip> Access: 2011-06-10 14:40:09.476805858 -0500 Modify: 2010-11-29 16:35:49.000000000 -0600 Change: 2011-05-31 11:31:14.050618001 -0500
That got me wondering if it would be useful to have the other 2 timestamps: Change and Access maybe. That got me thinking what would a Leo cli look like: $ leocli myLeoSettings.leo ~myLeoSettings~ ~myLeoSettings~ pwd myLeoSettings.leo ~myLeoSettings~ ls Options for new windows Leo debug settings @settings ~myLeoSettings~ cd @settings ~myLeoSettings-->@settings~ ls @string vim_trigger_event = disable <snip> @enabled-plugins ~myLeoSettings-->@settings~ cd @enabled-plugins Can't cd, @enabled-plugins is a node ~myLeoSettings-->@settings-->~ gvim @enabled-plugins <editor opens with contents of node, changes are saved back> ~myLeoSettings-->@settings~ cd .. ~myLeoSettings~ cd .. Already at root ~myLeoSettings~ cd @settings ~myLeoSettings-->@settings~ ls -l mtime <long ago> @string vim_trigger_event = disable <snip> mtime <just now> @enabled-plugins On and On. Does anyone else find that interesting? leoBridge offers gui-free access, probably almost all the required methods. A "stat" type element on a node could hold the timestamps, size etc. Maybe stat could include Ville's recent "class" attribute. Thanks, Kent -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
