newlispfanclub.alh.net

Thanks David Lutz, it seems that correct way to enable newlisp syntax is to put next code in ~/.vimrc (assuming syntax was saved in newlisp.vim) au BufNewFile,BufRead *.lsp,*.lisp setf newlisp au BufNewFile,BufRead *.lsp,*.lisp vmap <F5> <F5> au BufNewFile,BufRead *.lsp,*.lisp imap <F5> <ESC><F5> au...

Ok (I'm using vim as all-purpose editor too). So one should go through edit-quit-run cycle (or invoke edit from newlisp?). It seems that I simply need some practice to make less errors and to find them quickly. newlisp is so nicelly engineered that it's possible to memorize almost the whole library ...

Thanks, Lutz Another question - how do folks develop moderate sized programs in newLisp, what environment are you using, etc? newlisp-tk is very handy when creating small snippets (I'm used to Smalltalk, but it's definitely overkill for scripting), but I found a bit bothering to gather these pieces ...

Hi, all and thanks Lutz for a great software. I have a slightly funny behaviour of newlisp on FreeBSD - it creates files with execution flags. Is there any intention behind this or may be I'm doing something wrong? %newlisp newLISP v8.0.6 Copyright (c) 2004 Lutz Mueller. All rights reserved. > (writ...