This post discusses two vaguely-related topics: 1. The bookmark-find-all command will create bookmarks en masse.
2. @command-history nodes will preload commands into command history in an explicit order. *bookmark-find-all (bfa)* Imo, if bookmarks are to replace clones, there *must *be an analog of clone-find-all (cfa), say bookmark-find-all. This would create a bookmark for every node found in a find-all command. Like cfa, bfa would create the bookmarks as children of an organizer node. If the outline contains an @bookmarks node it would be reasonable to create the organizer node as the last child of the @bookmarks node. bfa must be implemented deep within Leo's find/replace code in leoFind.leo. It's on my list... The "official" cfa command searches the entire outline, but the newly-added c.cloneFindAllAtNode and c.cloneFindAllFlattenedAtNode helpers make it easy for @button cfa-x nodes to start (and thus limit) the search to a particular node and its followers. We must have similar helpers for bfa. The distinction between clone-find-all and clone-find-all-flattened does not exist for the bfa. *@command-history* At present, @command/button nodes preload their created commands using the @args add hack. This was a decent prototype, but it has obvious drawbacks. It would be more Leonine to add support for @command-history nodes. The body of such nodes would be an *ordered* list of commands to be preloaded into command history. This makes it much more convenient to specify the initial contents of the history list. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
