Date: Thu, 11 Mar 2004 22:19:47 +0100 From: Henrik W Lund <henrik.w.lund@broadpark.no> To: "Gary W. Swearingen" <underway@comcast.net> Cc: freebsd-questions@freebsd.org Subject: Re: XEmacs woes... SOLVED Message-ID: <4050D7F3.5000504@broadpark.no> In-Reply-To: <2nad2ng91e.d2n@mail.comcast.net> References: <404E4276.4070607@broadpark.no> <q9y8q9fiht.8q9@mail.comcast.net> <404F75B3.9040100@broadpark.no> <2nad2ng91e.d2n@mail.comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Gary W. Swearingen wrote:
| Henrik W Lund <henrik.w.lund@broadpark.no> writes:
|
|> Well, it generated output allright. Nothing that makes sense
|> (unless I sit down and learn an entire programming language,
|> which seems huge and cryptic, by the way), though. Here it is:
|>
|> Signaling: (invalid-regexp "Invalid syntax designator") ~
|> signal(invalid-regexp ("invalid syntax designator")) ~
|> byte-code("..." [kill-buffer buf signal data] 3) ~
|> find-file-noselect("/usr/home/henrik/devel/sdl/lesson1/tutorial1.cpp")
|>
|
|
| Some of that makes sense. It's just showing your a list of
| functions which had been called by other fuctions when it bailed
| out. It was obviously "find"ing your .cpp file, but that function
| then seems to be interpreting some "compiled" elisp, probably to
| process the C++ syntax with colors or whatever, and choked on some
| syntax it was not (due to its own bug?) not able to handle so it
| signaled an error with the error msg above in quotes. Now that I
| think of it, I once had a similar error where something couldn't
| handle my HTML. I never determined what was wrong, but changing
| the HTML "fixed" the problem. You could try messing with your .cpp
| file, or try to find a better fix by posting the "trace" to one of
| the emacs newsgroups. I'm not sure, but you might get a better
| trace (with several other function calls replacing the "byte-code"
| thing, if you try to get your emacs to use
| /usr/local/lib/xemacs-21.4.14/lisp/files.el rather than
| /usr/local/lib/xemacs-21.4.14/lisp/files.elc eg, by renaming the
| latter temporarily to files.elc.xxx. Assuming that you're trying
| to track down the .el file (called indirectly from
| find-file-noselect) which analyzes the C++ code.
|
| I give up.
The solution:
pkg_deinstall xemacs\*
portinstall xemacs
:-D
For some reason, it decided to work this time around. Go figure.
Anyways, thanks! I did learn some lisp, so I guess XEmacs is all right
after all. ;-)
- -Henrik W Lund
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFAUNfynzC5lcw9P3IRAm6FAKCx7g5Ldq+OkX20waszX3LAQm8ocQCeJ9As
oIJzvwOCL2JWg/pJykAbKlM=
=tfqd
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4050D7F3.5000504>