Re: XEmacs woes... SOLVED
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gary W. Swearingen wrote: | Henrik W Lund [EMAIL PROTECTED] 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 finding 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- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: XEmacs woes...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gary W. Swearingen wrote: | Henrik W Lund [EMAIL PROTECTED] writes: | | right after it has loaded view-less.el. I tried looking through | view-less.el, but to no avail. | | | You might try putting this in your .emacs file: | | (setq debug-on-error t) | | (Or before you read the file that started the problem, pull down | the Options/Troubleshooting menu and set the Debug on Error | button.) | | I think it will then stop on your error, leaving a stack track in | a lower window and I forget what in an upper window (maybe | view-less.el). | | Good luck, and don't fail to try Gnus (after considerable reading | of it's info). 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) ~ find-file(/usr/home/henrik/devel/sdl/lesson1/tutorial1.cpp nil) ~ call-interactively(find-file) ~ #compiled-function nil ...(4) [call-interactively toolbar-open-function] 2 call-interactively(toolbar-open) ~ release-and-activate-toolbar-button(#buttonup-event button1up) ~ call-interactively(release-and-activate-toolbar-button) And I thought C code was cryptic... Anyway, thanks for your help so far. - -Henrik W Lund -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFAT3WznzC5lcw9P3IRAmcUAJ0esJKk0pB1sZcZRPS8zAsVynv+cACfXzXq 9AudrzCUfYpB476hwwyaNZ8= =7CLx -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: XEmacs woes...
Henrik W Lund [EMAIL PROTECTED] 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 finding 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. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: XEmacs woes...
Hi, Is this with the cc-mode distributed with xemacs? Which version of xemacs? i tend to use xemacs' package manager for all elisp modules - you could try updating all of the related modules, it might help: Menu: Tools - Packages - Add download site, Tools - Packages - List and install Also, you don't an old .emacs file or .xemacs/xxx lying around that could break it. Did you try running without any own dot-files? Hope this helps, Palle --On tisdag, mars 09, 2004 23.17.26 +0100 Henrik W Lund [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Greetings!! Having installed XEmacs from ports, it's running fine, except for one thing: whenever I try to open an existing C/C++ file (I have syntax highlighting on), it refuses to open it, and gives me the error message: /Invalid regexp: Invalid syntax designator/ right after it has loaded view-less.el. I tried looking through view-less.el, but to no avail. Furthermore, if I create a C/C++ file, I can write as usual, and the # include lines get highlighted, but nothing else. For every keypress I make, the following error message is displayed: /Fontifying region... (invalid-regexp Invalid syntax designator) /If I turn off syntax highlighting for C/C++ altogether, it lets me work without errors (and without syntax highlighting, of course). Syntax highlighting for other modes (Lisp-mode, Makefile-mode, etc) works just fine. I've really exhausted all sources on this one, as the existing documentation does not provide information specific enough. I even tried downloading the cc-mode off of cc-mode.sourceforge.net, but to no avail. A glance through the .el files leaves me no wiser either. Does anyone know what the problem could be? XEmacs is kick-ass, but this thing is annoying me half to death (the one feature I will be using a lot of is the one feature that doesn't work). Thanks for any help! Henrik W Lund Public key for 0x9F30B995CC3D3F72 - -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.2.4 (FreeBSD) mQGiBEA1DzERBADEO+BpxeWo2PcAN8vFRWkUATB7aLZYy60NZPVYl4iQdi/PzV5O 2sRrXa9vFWHhPBkxPBmRkQ2q+6JwHkm0OUKVvbqE7N+/DW+i9nmJWAMFlCBraeV+ zZG47ygPGfEFkQmcBJjPyOloQL+AeiSF/UXc9zpTk/87O4UANQ2H7SDWwwCgujiA 26Z0xIEnKoOIPlHw5k0GzWUD/0+TSqlMRUfXpt6j6pY4ApZN+WC3uAvJobAMlhCC 8rnCw/SYze8A04bawiObSIa3KAWTn38XxPG0CoHxo2savC4seJZjeqlZx6zwCpe8 iM4ZNUaBlzQyGvyvImVRVW+cIE1TF1prHIXbMfbiGVgTnHL4dvcFu8oTshyLgX2U T/xPBACRoP03MpUaXax55dc7+jtApGXEI73S55nn0hUYPfE7Zs7FKYWWKpclEzMk /D1Ga7MGcIIjRJuQx0dZeTxmprZOxHTkZGJeglIsQMXRv2dtzIOxuGh9w2pABdXZ R6C05jaW851/SQklUIN18XJV6uw8wOs6zvCNYefxrx+2b20ScLRKSGVucmlrIFcg THVuZCAoUEdQIC0gYmVjYXVzZSBwcml2YWN5IG1hdHRlcnMpIDxoZW5yaWsudy5s dW5kQGJyb2FkcGFyay5ubz6IWwQTEQIAGwUCQDUPMQYLCQgHAwIDFQIDAxYCAQIe AQIXgAAKCRCfMLmVzD0/cpFzAJ4iFO5PYHPUyiKoIIoi7J+mwBSrzgCffasMqe2P 9rb9lGyyHKht6zj8cBaISQQTEQIACQUCQDaeaQIHAAAKCRDguFH/PPq0hJAIAJ9N 1tG7ELHSoZ7oLbfUC7LP0Z8nYQCeIlJSEavVZfQVxjdGN+O7xOIErEa5AQ0EQDUP ORAEALgbOmUUMiPVmIm6dy9In9qMOzIs9cD1U0CWs8ySSKDDkNKsam08AwDcPnTr DLfbwcaEEvgVHcedbcAM9lUssIYo1CJqYIn4blvZGjC/jDRSj2UTzgMUA68/bZzO XVziwxvDOC43pLjm013Khem9rtAIEp2GmI4CsX5TpTLj7I7XAAQNA/92qSaTjlbm oUBGZPLN3WaFiGtem/41xTgzpBh31Tn6yxaFghzfMHDiyDqMxsWbPkiKyNfu4N1S jPmKTStCSx0lMlxs2bOgy/1LtqcNq+3i3znXsGbpB1jgFuriO882zf4zATSNmJiy RWEJgNwsgHllSDNk6nOoDddR6hpULGKShIhGBBgRAgAGBQJANQ85AAoJEJ8wuZXM PT9y6jgAnjTGTTnutfhVvPrJ9u+sYBD/nTFvAJ44/StfAKJoWCjl7Jr4uQYbpEGz Sg== =+NK+ - -END PGP PUBLIC KEY BLOCK- -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFATkJ1nzC5lcw9P3IRAsOLAJ98vv/4KZY4YBnPi4D2ha/duhrKXwCfbw2i zfw3HVntl7a+FryIr677TIo= =7HM9 -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: XEmacs woes...
Henrik W Lund [EMAIL PROTECTED] writes: right after it has loaded view-less.el. I tried looking through view-less.el, but to no avail. You might try putting this in your .emacs file: (setq debug-on-error t) (Or before you read the file that started the problem, pull down the Options/Troubleshooting menu and set the Debug on Error button.) I think it will then stop on your error, leaving a stack track in a lower window and I forget what in an upper window (maybe view-less.el). Good luck, and don't fail to try Gnus (after considerable reading of it's info). ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]