I didn't find any "catalog" used in LeoPyRef.leo except for one plugin, and that used what was a clearly different catalog. Maybe this answers the question...
On Sunday, November 27, 2022 at 3:18:02 PM UTC-5 Thomas Passin wrote: > "Modes" are programming languages recognized by Leo, e.g., by the *@language > xx* directive. They are in the *modes* directory. They are for the most > part python files except for *clojure.xml* and *markdown.xml*. > > In the directory there is also a file named *catalog*. It lists most or > (maybe all) of the .py files as entries. The file starts with this comment: > > <!-- This is a mode catalog. Edit modes must be listed here, --> > <!-- otherwise they will not be available to jEdit. --> > > The entries look like this: > > <MODE NAME="javascript" FILE="javascript.xml" > FILE_NAME_GLOB="*.js" /> > > Now here is the point that caught my attention. Those *FILE* attributes > all end in .xml, but there are no such .xml files in the leo directory tree. > > I'm guessing that this catalog file was taken from jEdit or some other > source and that Leo has never used those .xml files. Leo could just > directly look for **'py* and *.xml* files in the directory and not ever > need the catalog. > > Is this speculation right, or does Leo actually use the catalog file? > -- 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/2e17749b-47c2-4d08-be79-2aa3abef856bn%40googlegroups.com.
