Hi all I am having difficulties with Jedit and the vex syntax macro from the exchange.I installed it and added
<MODE NAME=“vex” FILE=“vex.xml” FILE_NAME_GLOB=“*.vfl” />
To the catalogue file, when I start a new file I just get the error below.I figure I must of done something wrong but cannot figure what for the life of me.Is anyone else having problems ?
Rob
Jedit !
11536 12 0- circusmonkey
- Member
- 2624 posts
- Joined: Aug. 2006
- Offline
- altbighead
- Member
- 113 posts
- Joined: July 2005
- Offline
- David Gary
- Member
- 74 posts
- Joined: July 2005
- Offline
Hey guys.
it's maybe a java pb: have you got the latest version of Java installed on your PCs? ( you can dl it at java.com)
(i guess you have this problem while attempting to do the tuts of the vex dvd 1, right ?: i didn't mentioned that JEdit required Java environment, i remember saying it was Java-based, but i didn't spend time on this cos i didn't want to go too far from Houdini itself- sorry)
-d
it's maybe a java pb: have you got the latest version of Java installed on your PCs? ( you can dl it at java.com)
(i guess you have this problem while attempting to do the tuts of the vex dvd 1, right ?: i didn't mentioned that JEdit required Java environment, i remember saying it was Java-based, but i didn't spend time on this cos i didn't want to go too far from Houdini itself- sorry)
-d
- circusmonkey
- Member
- 2624 posts
- Joined: Aug. 2006
- Offline
- wolf_cub_one
- Member
- 44 posts
- Joined:
- Offline
- Alanw
- Member
- 320 posts
- Joined: Aug. 2007
- Offline
wolf_cub_one
Did anyone have a solution to this problem?
Just started the CMI VEX DVD1 and got jEdit installed on Ubuntu7.10, but got the same error as everyone else.
I just installed Jedit and the vex.xml syntax highlighting and it works fine. You need to open the vex.xml file, and when you check to see line 12 is actually the <?xml> tag.
Open any of the other “working” syntax mode files from the “modes” directory and copy + paste their top 2 lines.
<?xml version=“1.0”?>
<!DOCTYPE MODE SYSTEM “xmode.dtd”>
That clears up the error, and it appears to be working.
Jedit isn't the only text editor to support VEX. I personally use Cutter www.fundza.com, but it has the same functionality. You can press Alt+E and it will compile + produce an OTL for you using VCC. I'm sure you could do the same with macro's in Jedit though.
- wolf_cub_one
- Member
- 44 posts
- Joined:
- Offline
- wolf_cub_one
- Member
- 44 posts
- Joined:
- Offline
- Alanw
- Member
- 320 posts
- Joined: Aug. 2007
- Offline
- wolf_cub_one
- Member
- 44 posts
- Joined:
- Offline
- wolf_cub_one
- Member
- 44 posts
- Joined:
- Offline
- rdg
- Member
- 401 posts
- Joined:
- Offline
me just realised:
if you change the line in $HOME/.jedit/modes/catalog
from
<MODE NAME=“vex” FILE=“vex.xml” FILE_NAME_GLOB=“*.vfl” />
to
<MODE NAME=“vex” FILE=“vex.xml” FILE_NAME_GLOB=“*.{vfl,str}” />
jedit also highlights code when evoked from alt-e
Maybe of interest for someone else.
Georg
if you change the line in $HOME/.jedit/modes/catalog
from
<MODE NAME=“vex” FILE=“vex.xml” FILE_NAME_GLOB=“*.vfl” />
to
<MODE NAME=“vex” FILE=“vex.xml” FILE_NAME_GLOB=“*.{vfl,str}” />
jedit also highlights code when evoked from alt-e
Maybe of interest for someone else.
Georg
this is not a science fair.
- kuba
- Member
- 345 posts
- Joined:
- Offline
-
- Quick Links