xemacs and c++ //-type comments
The c++ mode in xemacs does not appear to recognize the double-slash comments in c++ code (these comments start with // and end at the following new-line -- like the '#' comment character in ksh scripts). Does anyone know if there is a patch or modification for the c++ mode so that it will recognize these comments (i.e. for the file /usr/lib/xemacs-19.14/lisp/modes/cc-mode.el) ? Thanks. -- Harmon
Re: xemacs and c++ //-type comments
[Please don't Cc me when replying to messages on the list] Harmon, On Sat, Mar 1 1997, root (you?) wrote: The c++ mode in xemacs does not appear to recognize the double-slash comments in c++ code (these comments start with // and end at the following new-line -- like the '#' comment character in ksh scripts). Works fine for me in C++ mode. AFAIK //-comments are illegal in ANSI C and Xemacs only helps you to adhere to that standard when it's buffer is in C-mode. Does anyone know if there is a patch or modification for the c++ mode so that it will recognize these comments (i.e. for the file /usr/lib/xemacs-19.14/lisp/modes/cc-mode.el) ? If your files are C++ source (e.g. class decls in .h files) put a line // -*- mode: C++ -*- at the top of your file to put the buffer into C++ major mode. -- Siggy -- Siggy Brentrup [EMAIL PROTECTED] aka: [EMAIL PROTECTED] PGP fingerprint = C8 95 66 8C 75 7E 10 A2 05 61 C7 7F 05 B6 A4 DF
Re: xemacs and c++ //-type comments
On Sat, 1 Mar 1997, root wrote: The c++ mode in xemacs does not appear to recognize the double-slash comments in c++ code (these comments start with // and end at the following new-line -- like the '#' comment character in ksh scripts). Yes it does, my 19.14 emacs seems to understand these comments fine. I'm not sure what you're doing. RTFM and check your settings, I've used 19.14 on both Solaris and Linux without problem with // commenting. Did you turn color on? Have you verified that you haven't made any changes to the standard .el files? If all else fails try to get the source and see if you can get the .el files from there (who knows, the Debian distribution you got MAY have a bug...) Will
