And how it is possible to specify setings in @file? As I understand every setting should be a single outline
2019-07-19 22:36 GMT+03:00, Chris George <[email protected]>: > I can think of several approaches. > > @outline-data tree-abbreviations in myLeoSettings.leo that is available to > all Leo files. > @button > @command > Point all files to an @file node and share the settings via a single text > file. ie. conf.py or a YAML file > > There may be reasons some of these approaches wouldn't work for your case. > But some might. > > HTH, > > Chris > > On Friday, July 19, 2019 at 11:09:33 AM UTC-7, gar wrote: >> >> Imagine you develop several tied software projects at the moment. >> Imagine they all use the same settings (like basic paths, colors, whatever >> >> else). >> >> In before-leo world you probably have several template files which you >> fill with current values and include into your projects and reuse settings >> >> in there >> (file.cfg.in -> file.cfg idiom, where file.cfg.in is under source control >> >> and file.cfg is ignored) >> And how to deal with this in leo? >> AFAIK it's impossible to include other .leo projects or their parts. >> >> How to implement settings/code reuse? >> Put everything into myLeoSettings.leo? >> > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/d03f3fa6-6ebb-4cf4-90f1-c73b128c44b7%40googlegroups.com. > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAC%2B8SVyK%2Bbsz0qPyfO5nznB6uvxy6oHXb7fYvCf5cpg9n%3DzbOg%40mail.gmail.com.
