Is there an ideal programming cycle for newLISP?

[dukester]

Hey all.....

I'm new to newLISP! I'm wondering if there's an ideal way to program in newLISP? With some other languages that I've used, I typically have to windows open:
1. vim editor
2. compiler

I edit my source code in one window; ALT TAB to the next window; UP ARROW for the latest CLI command (i.e. newLISP whatever.lsp); program output; ALT TAB to editor.

Is that what you guys do? I realize that some editors have the capability of piping the the current file to a pre-defined compiler. Sometimes setting these up can be a PITA ;)

Anyway, TIA for any pointers/suggestions/comments.L8r...

[HPW]

SHX in the last post here before yours ask similar questions:

http://www.alh.net/newlisp/phpbb/viewtopic.php?t=1637

Myself I use mostly ultraedit.
Sometimes also newlisp-tk.

[Lutz]

At the end of this page:

http://www.turtle.dds.nl/newlisp/index.html

you find a nice screenshot of running a shell inside a split window in Vim.

Lutz

[Lutz]

... and you find more about editor support here:

http://newlisp.org/index.cgi?Code_Contributions

Lutz

[dukester]

At the end of this page:

http://www.turtle.dds.nl/newlisp/index.html

you find a nice screenshot of running a shell inside a split window in Vim.

Lutz

I use Vim a lot when I'm on my FreeBSD box. So you edit the source code with Vim. You run the code from another xterm window? Or from within Vim itself? Never done the latter - how do you get _that_ to happen?

[cormullion]

late but....

I usually edit in an editor (TextWrangler at present) and hit the 'run' command. It works fine. Recently, trying to track down some error of mine, I've started running functions in the terminal. So:

[ I'm editing then I save ...]
[ Command-Tab to terminal running newlisp]
> (load "file.lsp")
> (debug (function-exp))

and then I'm in the debugger, stepping through the function. Although the debugger is simple, I like that simplicity.

I've put

Code: Select all

(trace-highlight "\027[0;32m" "\027[0;0m") 

into my init.lsp file, because I can never remember the codes. Now, when tracing a function, the current expression is in green... I'm starting to appreciate the way you can type in any expression at any point in the executing code.

[alex]

to cormullion
You have ANSI-console in Windows?

I want too :-)

my variant

Code: Select all

(trace-highlight "\219\219" "\219\219")

[cormullion]

no. Don't even have Windows... :-)

I was merely trying to say that I use an editor and then debug in a terminal. Sorry if i suggested otherwise...!

[dukester]

late but....

I usually edit in an editor (TextWrangler at present) and hit the 'run' command. It works fine. Recently, trying to track

So this 'run' command must be equivalent to other editors' tools option which allow you to set up a compiler/interpreter to execute the code?

down some error of mine, I've started running functions in the terminal. So:

[ I'm editing then I save ...]
[ Command-Tab to terminal running newlisp]
> (load "file.lsp")
> (debug (function-exp))

and then I'm in the debugger, stepping through the function. Although the debugger is simple, I like that simplicity.

Yep! that's what I've done in other languages in the past.

I've put

Code: Select all

(trace-highlight "\027[0;32m" "\027[0;0m") 

into my init.lsp file, because I can never remember the codes. Now, when tracing a function, the current expression is in green... I'm starting to appreciate the way you can type in any expression at any point in the executing code.

Cool. Ill have to try this.