On Tue, Jun 28, 2011 at 11:36 AM, Largo84 <[email protected]> wrote: > Consider a node headline: > > @file SomeFile.tex > > I would expect that Leo would auto-detect the TEX file extension but > it doesn't. Odd that the colorizer works (sometimes) but file write > doesn't create the proper comment characters (% for TEX) unless I > explicitly add @language tex.
My apologies for the long delay in responding. Rev 4568 of the trunk causes Leo's write logic to get the comment delimiters from the extension of the nearest enclosing @<file> node if no @language directive is in effect. That is, @language still has highest priority, but now the file extension takes precedence over the ultimate default, which is python. BTW, there already was similar code to determine the language to be use for the purposes of syntax coloring, but the new changes could be called even more important. Edward -- 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.
