newlispfanclub.alh.net

I love both newLISP and BBedit.

But, while I have newLISP working flawlessly with TextMate, I can't get BBedit to run a script from the #! menu. Rather, BBedit complains "File appears to lack proper shebang line."

(I have installed the BBedit plist file, which appears to be working.)

I'm on fully-patched OSX 10.7.2.

Any ideas?

Thanks,

Bob

The first line of every script should be

#!/usr/bin/env newlisp

or

#!/usr/bin/newlisp

What is the first line of your script?

cormullion wrote: #!/usr/bin/newlisp

What is the first line of your script?

This worked. I had a space after the "!". Duh.

Thanks much.

Bob

What code less module are you using in BBEdit for syntax highlighting?

I've tried to move to BBEdit for newLisp and I keep going back to TextMate for various reasons, not the least of which is auto-paren matching.

I'm using something based on this:

http://www.truerwords.net/articles/bbed ... odule.html

but it does tend to grind to halt on bigger files.

You could check out Sublime Text too - there's more than a hint of Textmate to it.

Care to share?

Mine is old and crappy and doesn't support any of the new keywords or proper variable highlighting as part of its syntax. I've been sticking with TextMate because the newLisp language Bundle just works (and I can add words and fix it when it doesn't, without having to figure out Ph.D. level code writing).

cormullion wrote:I'm using something based on this:

http://www.truerwords.net/articles/bbed ... odule.html

but it does tend to grind to halt on bigger files.

You could check out Sublime Text too - there's more than a hint of Textmate to it.

My version has nothing much except the new keywords, but still struggles to format longer files - the regex approach isn't very quick, I suppose. You can find it on github.

SublimeText accepts TextMate language bundles, by the way - if you understand the latter, you'll be able to customize the former.

By the way - notice the syntax highlighting for newLISP files on Github? Took ages for that to happen! And it still breaks on regex... :)