Does the vi package for newLISP work like slime+vi?
How about the emacs package for newLISP?
--hsm
Quote from: "hsmyers"
Does the vi package for newLISP work like slime+vi?
No, it is syntax highlighter, nothing more.
Quote from: "hsmyers"
How about the emacs package for newLISP?
No idea. Never using emacs.
Yeah, it runs as a minor mode, but's buggy. I fixed one problem, but I never use it. I don't know if the one on my site is the newest or not:
http://artfulcode.net/projects/newlisp-mode-emacs/
Quote from: "Jeff"
Yeah, it runs as a minor mode, but's buggy. I fixed one problem, but I never use it. I don't know if the one on my site is the newest or not:
http://artfulcode.net/projects/newlisp-mode-emacs/
Looks like I need to do another release, 'cuz I've written the emacs
mode, and am running newlisp inside of emacs and am successfully
evaluating code, but don't know about other issues.
Yo! Folks! If you have a problem, send me an email, or a PM.
I can go for weeks without looking at this forum.
P.S. I use linux. Haven't tested for windows. Sorry.
tim
i just use the normal inferior lisp mode inside emacs.
all you have to do is to set inferior-lisp-program to point to newlisp (with -C
option).
(load-library "inf-lisp")
(setq inferior-lisp-program "C:/users/bob/bin/newlisp.bat")
the newlisp.bat just has this:
c:"program files"newlispnewlisp.exe -C
then i can just edit any newlisp program in emacs and evaluate any selected
region by just doing control-C control-R. this is typically all i need. i use the same method for clisp too. i don't use slime. it's too complicated and buggy.
inferior lisp mode is simple and does all that i want, which is to interact
with REPL inside emacs.
i used to use newlisp mode by Tim Johnson, but i found it unnecessary for my needs.
Damn! It's a good thing that I actually like emacs ;) Otherwise I'd be in a world of hurt. I dislike the newLISP java interface for a variety of reasons and can leverage emacs over it, Common Lisp and Scheme. I like your approach, I'll try it shortly...
--hsm
Quote from: "hsmyers"
Damn! It's a good thing that I actually like emacs ;) Otherwise I'd be in a world of hurt. I dislike the newLISP java interface for a variety of reasons and can leverage emacs over it, Common Lisp and Scheme. I like your approach, I'll try it shortly...
--hsm
I've made changes to the newlisp mode. Common lisp mode certainly
doesn't meet my needs - and I'm actually coding in newlisp now. If anyone
wants my current newlisp mode codebase, just send me an email and I
will get it to you.
I suspect that once I get to the point where I'm delivering services to
clients using newlisp, emacs newlisp-mode will be pretty robust.
BTW: The emacs Gods require C-c keybindings to make the mode
possibly eligible for for bundling with the distro, but that's not as productive as
simpler rebindings - such as using Super and Hyper modifiers. In fact
I've a thin layer built over the mode keybindings that uses both those
modifiers and a standalone numeric keypad programmed for emacs.
My email is tim@johnsons-web.com
Additionally, I'd suspect that the newlisp Java interface could be interfaced
with emacs and with CUA-style bindings (to hell with the emacs Gods),
one could have a product that even newlispers who hate emacs might
like. Would just take will and time.
Tim,
Send them to me and I'll put them up on Artful Code with attribution and a site link, if you like.
Jeff
Quote
I'd suspect that the newlisp Java interface could be interfaced with emacs
You don't need the java front-end at all to run programs using the guiserver.jar library. You can run any of the programs you find in /usr/share/newlisp/guiserver or in C:Program Filesnewlispguiserver out of Emacs or Vi or from the terminal command line like any other newLISP program.
Quote from: "Jeff"
Tim,
Send them to me and I'll put them up on Artful Code with attribution and a site link, if you like.
Jeff
OK. There will now be two files, got rid of the on-demand documentation,
too many parsing issues.
Let me look thru the code and add what annotation I might find necessary,
and I will put a link to a tar/zip file in this thread - sometime later
today or tomorrow.
Thanks
Tim
Would you mind adding eval buffer to the menu? Also, the parenface file was missing from the tarball on the main site, so I commented out the related code.
Quote from: "Jeff"
Would you mind adding eval buffer to the menu? Also, the parenface file was missing from the tarball on the main site, so I commented out the related code.
eval buffer is currently in the menu as "Load File", (C-c C-e b), I will
change it to "Evaluate Buffer". And I will make sure to include tj-parenface.
Tim
http://www.johnsons-web.com/demo/newlisp/newlisp.tgz
Most windows archivers should be able to unpack this.
Please note the following:
Quote
Please contact me at:
tim@johnsons-web.com
If there are any problems. I recommend that you also post the questions,
comments or caveats at newLISP Fan Club Forum Index -> newLISP newS, but
since I don't always check in at the Forum, shoot me an email also. This has
not been thoroughly tested, any bugs that you find and report or fix will
improve the product. Furthermore there is the possibility that I may have
mistakenly inserted function calls from other elisp modules that I've written,
if you find references to them, I'll get the code imported into the mode.
On-demand documentation has been removed. Too much trouble with parsing.
This has *only* been tested on linux. I now longer use Xemacs, any references
in the code to Xemacs should be considered incidental.
Expect two menus: "Newlisp" (functions and bindings) and
"Index" (function indexes). Also, note that the rather cumbersome
key bindings are made to be consistant with emacs protocols. If anyone
needs help or ideas regarding alternate key bindings (recommended),
I will help if I can or questions can be posted to newsgroup gnu.emacs.help.
You will want to delete the keywords from newlisp-user-keywords-regexp
and put in your own....
Thanks
Tim
P.S. The following functions:
newlisp-indent-and-move-next, newlisp-indent-and-move-back,
newlisp-prev-opening-parens, newlisp-next-opening-parens,
are not bound to any keys, it's recommended at this time that
they could be bound to key that are most convenient for the user.
Tim,
I added it to artful code and made a few changes myself. All my changes are commented. Here is a link:
http://www.artfulcode.net/projects/newlisp-mode-emacs/
Thanks Jeff. I really like the incremental evaluation.
And I will remember to byte-compile.
Cheers
Tim