From: Alan Mackenzie <acm@muc.de>
Cc: bug-cc-mode@gnu.org, emacs-devel <emacs-devel@gnu.org>
Subject: Re: comment-start redefined in cc-langs.el
Date: Tue, 2 May 2006 07:58:55 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.3.96.1060502074804.310A-100000@acm.acm> (raw)
In-Reply-To: <44537B33.7080600@gmx.at>
Hi, Martin!
On Sat, 29 Apr 2006, martin rudalics wrote:
[ .... ]
>Now load cc-mode in a new buffer, return to scratch, and do again
>C-h v comment-start RET
>gets me
>comment-start is a variable defined in `cc-engine.el'
>...
Yes, me too. This is indeed not funny (Ha ha ha ha!) I'm not sure why
it reports cc-engine.el, but better just to fix it.
>If I now click on `cc-engine.el' I am told
>find-function-search-for-symbol: Cannot find definition of
>`comment-start' in library `cc-engine.el'
The definition is actually in cc-langs.el, ~L1106:
(c-lang-defvar comment-start (c-lang-const comment-start)
'dont-doc)
What seems needed is a new macro c-lang-SETvar, a sister to
c-lang-defvar. I'll write this.
>The same holds for `comment-end' and `comment-start-skip'.
Yes, indeed. A quick grep for "(c-lang-defvar " reveals that these are
the only non-CC Mode variables redefined in this way.
>Would it be possible to rename these to `c-comment-start',
>`c-comment-end', and `c-comment-start-skip' in `cc-langs.el'?
No, that's not the right thing. The idea is to give the standard Emacs
variables the appropriate CC Mode settings (different for each CC mode).
Thanks for the bug report.
--
Alan Mackenzie (Munich, Germany)
next prev parent reply other threads:[~2006-05-02 7:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-29 14:41 comment-start redefined in cc-langs.el martin rudalics
2006-05-02 7:58 ` Alan Mackenzie [this message]
2006-05-02 12:57 ` martin rudalics
2006-05-02 15:55 ` Alan Mackenzie
2006-07-20 10:44 ` Alan Mackenzie
2006-07-21 16:05 ` martin rudalics
2006-07-21 22:52 ` Alan Mackenzie
2006-07-21 22:13 ` martin rudalics
2006-07-24 6:59 ` martin rudalics
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.3.96.1060502074804.310A-100000@acm.acm \
--to=acm@muc.de \
--cc=bug-cc-mode@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).