Your message dated Thu, 23 Jan 2014 04:27:09 +0000
with message-id <[email protected]>
and subject line Closing old emacs21 bugs
has caused the Debian Bug report #192684,
regarding emacs21 and c-comment-start-regexp
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
192684: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=192684
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: emacs20
Version: 20.7-13.1

I hope this isn't just a case of me doing something wrong, but after 8
hours of trying to trace elisp code, I can't seem to find anything else.


I'm trying to extend the c-mode "fill-paragraph" functionality to understand
a comment block using "//!" at the start (for Doxygen).  As near as I can
tell, my savior is:

        c-comment-start-regexp 
            This buffer-local variable specifies how to recognize
            the start of a comment. 

I've changed this variable to:

        c-comment-start-regexp's value is 
        "/[/*][!]?"
        Local in buffer dataio.c; global value is 
        "/[/*]"

        Documentation:
        not documented as a variable.

        Defined in `cc-langs'.

But when I do M-q, it behave the same as it did before I appended the "[!]?".

Before:
//!
//! A "DataIo" object is an abstract input/output device.  It allows other code
//! to run without knowing any specifics about the underlying driver, thus
//! providing the ability to write code much as one would use standard i/o
//! paths under unix or dos.
//!

After:
//!  ! A "DataIo" object is an abstract input/output device.  It allows other
//code ! to run without knowing any specifics about the underlying driver,
//thus ! providing the ability to write code much as one would use standard
//i/o ! paths under unix or dos.  !


Here's what I've learned (I think :-) by my attempts to debug elisp...

In the function "c-fill-paragraph" (cc-cmds.el), the "c-comment-start-regexp"
variable is not referenced until line #1645.  However, the function doesn't
seem to get down there as the original "if" on line #1594 appears to be true
and the code block starting at line #1597 gets executed instead.

                                          Brian
                                 ( [email protected] )

-------------------------------------------------------------------------------
  Diplomacy is the art of saying "nice doggy!"...  until you can find a rock.


--- End Message ---
--- Begin Message ---
Hi! I'm closing this bug, since it affected emacs21, and the current
version is 23. If you still encounter this problem, please feel free to
re-open it and move it to the appropriate package, or ask me to do it.

 Solveig

--- End Message ---

Reply via email to