medit syntax highlight
Brought to you by:
emuntyan
Menu
▾
▴
Hi,
I wanted to use medit for octave/matlab files. I was wondering if there's a way to use gtksourceview .lang files for medit or if there's a syntax highlight for matlab file ready for medit?
Please try this one (it's from gtksourceview):
http://mooedit.sourceforge.net/hg/moo?f=-1;file=moo/mooedit/syntax/octave.lang;style=raw
Drop it into $prefix/share/moo/syntax or ~/.medit/syntax/ .
Wow !!
Thanks it works great :-)
Hi there, I've just compiled and installed medit on Ubuntu 7.04 and got it up and running except that there's no syntax highlighting available and no languages in the list in prefs form. I can see all the .lang files are the in /usr/local/share/moo/language-specs and syntax highlighting is working in gedit which I believe uses the same component for it... does anyone here know what might be the problem?
It doesn't share the library with gedit, so what gedit does or does not won't help here.
Few things: did you do 'make install'? Did you have libxml2-dev when compiled medit? Configure should have said something like "use xml ....... no" at the end, if you don't have libxml2. Do you see some warnings when starting medit from console?
Thanks very much, that did the trick ;-)
On Ubuntu you need to first,
apt-get install libc6-dev libgtk2.0-dev libxml2-dev gettext intltool
and then ./configure && make && make install
I've tried adding a new syntax-highlighting scheme by modifying a copy of the Tango.xml scheme, but the new one doesn't show up in medit's dropdown list. What else needs to be done apart from create the xml file in the same place as the others and change the id and _name attributes in the content? Thanks, Aran.
No worries, I found the problem - they don't show up if the XML is invalid and I had referenced a colour where a style was required ;-)
Glad you sorted it out :)
In general, medit doesn't show dialogs or something in such cases but spits warnings to console. So if something like this is happening, first thing is to start it from terminal and see what happens. If there's silence, *then* something is wrong.