So basically that means you can't reliably use Leo's @file nodes for Elixir adn Erlang source code?
On Monday, September 16, 2024 at 4:46:09 PM UTC+2 Edward K. Ream wrote: > On Mon, Sep 16, 2024 at 9:05 AM Thomas Passin <[email protected]> wrote: > > Looking at the test erlang file, I see that the "<< ... >> " syntax seems >> to be an essential part. I had at first thought they were symbols that had >> not been escaped by the XML ingesting code, but I see that was wrong. I >> wonder if the section delineator characters "<< .... >> " could be changed >> using a directive, much like the comment character can be changed. Perhaps >> that would not be too much of a code change? >> > > Good question. Maybe 20+ years ago Leo had some escapes that roughly did > the same thing. > > One of the best design decisions I ever made was to eliminate those > hacks/conventions. There is no way to read @<file> nodes with *any* kind > of exception. I'm not going to change my mind about this while I live. > > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/cbbd9a6c-ae16-46f1-b695-a1b5314c8c98n%40googlegroups.com.
