From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Alan Mackenzie <acm@muc.de>
Cc: 21465@debbugs.gnu.org
Subject: bug#21465: [PATCH] CC-modes hierarchy
Date: Mon, 14 Sep 2015 21:06:06 -0400 [thread overview]
Message-ID: <jwvh9mw338p.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <20150914193349.13729.qmail@mail.muc.de> (Alan Mackenzie's message of "14 Sep 2015 19:33:49 -0000")
> c-after-font-lock-init surely isn't broken. c-after-change is ALWAYS on
> after-change-functions.
No, it's not. Not in my sm-awk-mode which derives from awk-mode.
Or rather, I don't want it there and c-after-font-lock-init forces it
down my throat again after I removed it.
> Without it, CC Mode simply wouldn't function.
It does.
Besides, my patch does not remove c-after-change from
after-change-functions. It just stops c-after-font-lock-init from
re-adding it if someone decided to remove it. AFAIK c-after-change is
never removed from after-change-functions by accident, so re-adding it
blindly is a bug.
>> AFAIK this patch has no issues w.r.t compatibility since it relies on
>> behavior of define-derived-mode which has existed since "for ever".
>> But it hasn't seen much testing, admittedly (except for my own personal use).
> The question is, will XEmacs's define-derived-mode work?
The text you quote is my answer to the question.
> By the way, abbrev mode is used to expand "else" and "while" to themselves
> + re-indentation. There are one or two other keywords handled likewise.
> This isn't something either of us like, but doesn't seem urgent enough
> to get round to fixing.
Indeed, I don't think it's urgent to fix it, but I think it deserves
a comment.
Stefan
next prev parent reply other threads:[~2015-09-15 1:06 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvh9mw338p.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=21465@debbugs.gnu.org \
--cc=acm@muc.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.