On Mon, Oct 27, 2008 at 8:46 PM, Daniel Clark <[EMAIL PROTECTED]> wrote:
> So if I want to @shadow a file that has lines like: > > cat << EOF >> cdebootstrap/suites > > I'm just screwed? You have several options, including: 1. Use @shadow and revise code to avoid << and >> on the same line. 2. Use @noref for "problematic" files. 3. Use one of several Leo plugins to manage script files. Consider the read_only_nodes or at_folder plugins: http://webpages.charter.net/edreamleo/plugins.html#nodes Note: using some kind of escape mechanism for << and >> implies having the ability to change (if only slightly) the contents of the file. If you can do that, option 1 applies. If not, options 2 and 3 apply. Edward P.S. Longer term, some extensions to Leo could be considered. A. Stephen suggests extending the role of the @verbatim *sentinel*. An @verbatim *directive* would, unless I am mistaken, create an @@verbatim sentinel. This could probably be made to work cleanly, though it would imply significant changes to Leo's fundamental read/write code. But in your use case, it's not clear to me that adding @verbatim directives would be preferable to putting << and >> on separate lines... B. Something like @shadow-noref, could have exactly the same read logic as @shadow, and the same write logic as @noref. This would give you an "escape" that applies to an entire file. The @shadow algorithm will work with regardless of the meaning of '<<' and '>>'. In fact, the fundamental @shadow algorithm knows nothing about Leo section references or markup. It does know about sentinels, but in a minimalist way. In fact this "lack of knowledge" is what makes @shadow work so well. Bernhard Mulder's algorithm is pure genius. I am not eager to do either A or B, but I am not ruling them out completely. EKR --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
