ViM syntax file?

[Lutz]

Thanks for the explanations how to register/install newlisp.vim with its own name. I knew there had to be a better way than renaming the file.



Regarding line numbers in error statements: for errors during runtime there are no line numbers available as all source is compiled lisp cells in memory. But in the case of the "missing paren" error I may be able display text starting at an earlier position. I will look into it.



Lutz

[pjot]

The 'exit' keyword is not recognized.

[Lutz]

I added 'exit' and the new 'dup' from version 8.0.12 and versioned it as 1.03 at : http://www.newlisp.org/code/newlisp.vim.txt">http://www.newlisp.org/code/newlisp.vim.txt nomally . David will work that in his 'official' version at http://www.geocities.com/excaliborus/">http://www.geocities.com/excaliborus/



Lutz

[pjot]

I noticed that symbols like >, <, = and also combinations like >=, <= etc. are highlighted.



But not this combination: !=



Maybe this should be in the syntaxfile as well?

[pjot]

And maybe also words like 'true'? Or 'nil'? These are currently not recognized.

[newdep]

I Just love this highlighting ;-)

[Lutz]

me too, :-)  http://www.newlisp.org/code/newlisp.vim.txt">http://www.newlisp.org/code/newlisp.vim.txt



Lutz

[pjot]

Me too... that's why I am nagging about it ;-)



Anyway, this new syntax file still does not recognize the != combination.... sorry to nag again...

[pjot]

I see that the != is in the syntax file but gVIM does not highlight it... maybe it's a bug in gVIM?

[Lutz]

it works on my machine in WinXP/Cygwin and on Linux Mandrake 9.2. May be some other Vim setting in your .vmrc ? Are you really using the correct file? try renaming newlisp.vim to lisp.vim



Lutz

[pjot]

Well, I renamed the 'newlisp.vim' file to 'lisp.vim' and indeed, now it's ok.



This seems to be the only way then? While if I state ":set syntax=newlisp" with the old file name newlisp.vim, then the ecalamation marks are not highlighted (e.g. '!' and '!='). Also changes in 'filetype.vim' did not change this situation. Maybe the original 'lisp.vim' is conflicting with 'newlisp.vim'?



But anyway, it works now, thanx.

[Lutz]

Excalibor posted a .vimrc a while ago to tweak this stuff, but I also never got it working with newlisp.vim and also had to rename it to lisp.vim. I guess it depends on the Vim version (there are about a million out there) and other local settings and IANAVE :-) .



Lutz

[pjot]

Hi Lutz,



Hacking with the memory stuff and crashes, I noticed that the 3 hacking commands are not recognized either (e.g. 'dump', 'address' and 'cpymem'). I'm not sure if it's a good idea to put them in the syntax file, but maybe you give it a thought?



Peter

[Lutz]

I should probably put them in the syntax file. It may alert users, if they use these words that they are used elsewhere.



Lutz