On Sun, Jul 6, 2014 at 4:04 AM, Fidel N <fidelpe...@gmail.com> wrote: > Hi all: > Im having trouble to keep Leo updated because of this, and wanted to ask if > someone can think of a way around. [big snip] > Is there a way I could still import files that way, without having to touch > LeoPyRef?
I think you are going to really like this answer: use a local copy of LeoPyRef.leo, by convention called leoPy.leo: http://leoeditor.com/FAQ.html#how-should-i-use-leo-with-bzr-git-hg-svn-cvs The third bullet point is: The repository contains reference .leo files. These reference files should contain nothing but @file nodes. Reference files should change only when new external files get added to the project. Leo’s git repository and Leo distributions contain the following reference files: LeoPyRef.leo, LeoPluginsRef.leo and leoGuiPluginsRef.leo. Developers should use local copies of reference files for their own work. For example, instead of using LeoPyRef.leo directly, I use a copy called LeoPy.leo. HTH. 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
