Hi, maybe this seems rather stupid to you, but as far as I know there is no rookie group to ask this kind of questions. Actually I am not that new to leo, at least I am observing this group very closely and posting from time to time for several years now AND using leo of course ever since. Although it doesn't seem very smart to you that I still did not get e.g. rst but more importantly how you guys manage it to work together with non leo developer folks ?
Use case: I need to work with different groups on different kind of source code repositories in different languages (C/C++, JAVA, JavaFX, Python, Perl, bash) So a lot of divers cloned and updated local working directories (git,mercurial,bzr,svn ...) with fast paced changes in files as well as in dir structure. To make things worse, most folks are not too tolerant about leo sentinels inside additional comment lines in the code. That make it seem almost impossible for me to keep up with leo to reflect these changes fast enough, cause I seem to have to keep the dirs in synch manually. Big question for me would be: Is there any mechanism that lets me read in a whole source tree and keep that automatically in synch without spitting all the sentinels into the files I need to push after I changed someth.? Maybe kind of this question got asked already but I am not aware of a solution that would make that problem go away. Especially when you guys refer to shadow nodes as "unreliable". How are you doing it ? best Stefan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
