Emacs and newLsip questions(/wishlist)

Started by prio, June 13, 2006, 04:10:39 AM

Previous topic - Next topic

prio

Hi,

Some newbie questions. I have been trying to get Tim's emacs mode to load but I get the following error on startup. Using emacs 21.3 on Windows. I also got this error on Linux.
Quote
Debugger entered--Lisp error: (error "Invalid escape character syntax")

  eval-buffer(#<buffer  *load*<2>> nil "nl-docstrings" nil t)

  load-with-code-conversion("c:/home/emacs-21.3/lisp/nl-docstrings.el" "nl-docstrings" nil t)

  require(nl-docstrings)

  eval-buffer(#<buffer  *load*> nil "~/.emacs" nil t)

  load-with-code-conversion("c:/.emacs" "~/.emacs" t t)

  load("~/.emacs" t t)

Anyone any ideas?

I have hacked scheme.el in the mean time and it seems to be working ok.



What  I would like to have is a key sequence which would load the current buffers file into a running newLisp instance in another buffer, is this possible?

I would also like to have a key sequnce to show documentation for the function my cursor is currently at.



Has anyone anything like this running that they could share with us newLisp/emacs newbies in the crowd?



Thanks.

Tim Johnson

#1
Hi Prio:

I don't monitor this forum regularly and didn't even know if anyone was using the mode. So... in the future if anyone has any questions about the mode, send me a 'private message' or email me directly at

tim@johnsons-web.com



I recommend for the time being that you comment out the form that loads nl-docstrings.



I have rewritten this mode from scratch and will upload the new mode as soon as time permits for me. One of the problems with the first version of the mode was that emacs and xemacs handled escaping of certain characters rather differently.



I don't use windows, so I'll need some feedback on how the inferior mode works on that OS.



Sorry for the inconveniences. For the time being: comment out as

follows:

;; (require 'nl-docstrings)



and I will post as soon as I have the revisions uploaded.

regards

tim
Programmer since 1987. Unix environment.

prio

#2
Thanks Tim. I only use windows at work and I was having the same problem on Mac OS X and Linux at home. I look forward to trying out your next version.