From owner-freebsd-questions@FreeBSD.ORG Thu Mar 11 13:14:21 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD77A16A4CE for ; Thu, 11 Mar 2004 13:14:21 -0800 (PST) Received: from mail.broadpark.no (mail.broadpark.no [217.13.4.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DC4143D1F for ; Thu, 11 Mar 2004 13:14:21 -0800 (PST) (envelope-from henrik.w.lund@broadpark.no) Received: from broadpark.no (61.80-202-129.nextgentel.com [80.202.129.61]) by mail.broadpark.no (Postfix) with ESMTP id 2E9B07E12; Thu, 11 Mar 2004 22:14:20 +0100 (MET) Message-ID: <4050D7F3.5000504@broadpark.no> Date: Thu, 11 Mar 2004 22:19:47 +0100 From: Henrik W Lund User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040224 X-Accept-Language: no, en-us, en MIME-Version: 1.0 To: "Gary W. Swearingen" References: <404E4276.4070607@broadpark.no> <404F75B3.9040100@broadpark.no> <2nad2ng91e.d2n@mail.comcast.net> In-Reply-To: <2nad2ng91e.d2n@mail.comcast.net> X-Enigmail-Version: 0.82.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: XEmacs woes... SOLVED X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Mar 2004 21:14:22 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Gary W. Swearingen wrote: | Henrik W Lund 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-----