search

dongs0104 / qlcolorcode

Automatically exported from code.google.com/p/qlcolorcode
0 stars 0 forks source link

Language definiton for IDL #26

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Love the plugin.

What would be nice would be to have support for IDL (I know it recognizes
the file type, but I mean support for syntax highlighting).

I've written a language definition file for IDL (attached).  I'm not
claiming it's perfect but it does a pretty good job.  At the moment I've
called it pro.lang and I put it in the override/langDefs directory where it
overrides the default language for .pro files (Prolog).  Unfortunately both
file types use the same extension, but at a pinch you could probably use
the same test (in colorize.sh) used to distinguish Matlab and Objective C
files with the .m extension (the prefix for comments in IDL is ';').

Original issue reported on code.google.com by chris.ri...@gmail.com on 24 Jun 2008 at 1:02

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by n8gray@gmail.com on 7 Jan 2009 at 7:46

GoogleCodeExporter commented 8 years ago 
I'm confused.  Highlight says it supports IDL on the language support page.  Is 
that the same IDL you're talking 
about here?

Original comment by n8gray@gmail.com on 9 Jan 2009 at 10:57

GoogleCodeExporter commented 8 years ago 
No - idl.lang is for a different language (I'm guessing it's Interface 
Description
Language).  I'm talking about Interactive Data Language (www.ittvis.com/idl/) 
which
is commonly used in scientific fields.  Confusingly, both are known primarily 
by the
same acronym.

Sorry, should have been more clear from the start.

Original comment by chris.ri...@gmail.com on 11 Jan 2009 at 3:17

GoogleCodeExporter commented 8 years ago 
I can confirm that .pro files are being incorrectly interpreted as Interface 
Description Language, which typically 
uses a '.idl' extension.  That said, I'm not sure the latter is widely enough 
used to merit default inclusion in 
QLColorCode, so I'd vote for switching 'pro' files to pro.lang and dropping the 
"other" IDL.   pro.lang works for 
me (if I simply replace idl.lang with it).

Great plugin, by the way!

Original comment by jdtsm...@gmail.com on 10 Mar 2009 at 8:41

GoogleCodeExporter commented 8 years ago 
Highlight 2.10 now supports Interactive Data Language (IDL) natively which 
might make
it easier to incorporate into qlcolorcode:

http://www.andre-simon.de/doku/highlight/en/highlight_changelog.html

They are using the naming convention of vim and are calling the language 
definition
"idlang.lang" for Interactive Data Language.

Original comment by bobby.me...@gmail.com on 21 Jul 2009 at 4:29

GoogleCodeExporter commented 8 years ago 
Fixed in version 2.0.  Thanks!

Original comment by n8gray@gmail.com on 17 Sep 2009 at 5:48