From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Mark Oteiza <mvoteiza@udel.edu>
Cc: 21465@debbugs.gnu.org
Subject: bug#21465: [PATCH] CC-modes hierarchy
Date: Sun, 13 Sep 2015 09:25:53 -0400 [thread overview]
Message-ID: <jwv7fnufo5y.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <87pp1neg2k.fsf@udel.edu> (Mark Oteiza's message of "Sat, 12 Sep 2015 12:51:47 -0400")
> It is not clear to me how to adapt a 3rd party derived mode to
> this.
Hmm... I'm missing something. I don't see how your problem is linked to
my patch?
> For mode derivation, either I have
> (define-derived-mode foo++-mode c++-mode "Foo++"
> ...)
> In which case there will be a parent c++-mode-map and a C++ menu present
But that's already the case with the code in (say) Emacs-24, no?
> when there shouldn't be, or:
> (define-derived-mode foo++-mode c-derivative-mode "Foo++"
> ...)
> and fontification is broken.
How is it broken?
Stefan
next prev parent reply other threads:[~2015-09-13 13:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-12 2:32 bug#21465: [PATCH] CC-modes hierarchy Stefan Monnier
2015-09-12 16:51 ` Mark Oteiza
2015-09-13 13:25 ` Stefan Monnier [this message]
2015-09-13 16:06 ` Mark Oteiza
2015-09-13 20:24 ` Stefan Monnier
2015-09-13 21:18 ` Mark Oteiza
[not found] ` <mailman.971.1442025193.19560.bug-gnu-emacs@gnu.org>
2015-09-14 19:33 ` Alan Mackenzie
2015-09-15 1:06 ` Stefan Monnier
2015-09-16 13:57 ` Alan Mackenzie
2015-09-17 1:49 ` Stefan Monnier
2015-09-17 12:30 ` Alan Mackenzie
2015-10-09 20:35 ` Stefan Monnier
2015-10-09 20:49 ` Stefan Monnier
[not found] ` <jwva8rrsrsu.fsf-monnier+emacsbugs@gnu.org>
2020-09-07 16:52 ` Lars Ingebrigtsen
2020-09-07 20:03 ` Alan Mackenzie
2020-09-07 20:40 ` Stefan Monnier
2020-09-08 10:11 ` Lars Ingebrigtsen
2015-09-15 8:46 ` Zhang Kai Yu
2015-09-19 18:43 ` Jostein Kjønigsen
2015-09-20 13:35 ` Stefan Monnier
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=jwv7fnufo5y.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=21465@debbugs.gnu.org \
--cc=mvoteiza@udel.edu \
/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).