On 10/20/08, Danny <[EMAIL PROTECTED]> wrote:
> Just starting to look at leo, and can't seem to figure out how to do
>  the basic use case of importing a project (aka a directory tree of
>  associated files, while ignoring files or directories with a certain
>  pattern, like subversion's .svn) and then keeping it in sync as other
>  people make file and directory deletions and additions to the tree.
>
>  By reading the doc it seems like I would want a big hierarchy of
>  @shadow nodes, but I haven't been able to find any procedure on how to
>  create those and then keep it in sync with the filesystem-based
>  reality; and manually doing this with 100s of files on a daily basis
>  would seem to be silly, so I'm guessing I've managed to miss something
>  obvious.

Looks like http://leo.zwiki.org/CreateShadows may be at least the
initial creation part of what I was looking for, although I'm sort of
surprised that what would seem to me to be such a routine activity
wouldn't be included in the base distribution, which leads to the
question of if I am just thinking about how Leo is used in the wrong
way.

>  Also, is there any way to get either tab-completion or a dialog box
>  when manually making nodes that reference files (e.g. @shadow /etc/
>  pass<tab> to create a node for the /etc/passwd file)?

Judging by the second round of searching this just doesn't exist, so
consider it a polite feature request :-)

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to