On Thu, 24 Apr 2008 06:05:12 -0500 "Edward K. Ream" <[EMAIL PROTECTED]> wrote:
> I assume you are asking about .css files specifically, and not > generally about any "unknown" file type for which there is no @auto > importer. Yes and no, I was thinking that for any file name/extension that can be mapped to one of the syntax highlighting modes in leo/modes it would be nice if auto set the language. So maybe a matter of changing how the default @auto (for file types for which there is no importer) works, probably still something like you describe, but a generic thing. > Given the importance of .css files, it would make sense to do this. > The easy way would be to define an importer for .css, then modify > > Code-->Core classes...-->@thin leoImport.py--><< class > leoImportCommands > >>-->Import-->createOutline (leoImport) > > to recognize this file type. Many scanners, such as the cScanner > class, can be defined in a single node. The ctor simply sets a few > constants that guides the general parser. Note the 'language' > argument to the base class ctor. The general code generator uses this > arg to create the @language directive. Care to create a branch for > this? :-) Maybe, I have some cleo todos I should attempt first probably, but I'll put it on the list. Cheers -Terry --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
