From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Alan Mackenzie <acm@muc.de>
Cc: bug-cc-mode@gnu.org, emacs-devel@gnu.org
Subject: Re: Reify the cc-mode-common into an actual parent mode
Date: Sat, 28 May 2016 13:51:20 -0400 [thread overview]
Message-ID: <jwvzirankh6.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20160528113003.GA2950@acm.fritz.box> (Alan Mackenzie's message of "Sat, 28 May 2016 11:30:03 +0000")
> Did I?
Maybe not exactly in those terms, but you did seem to come around to the
idea since there seemed to be enough code to be shared this way.
> `c-make-inherited-keymap' is not obsolete, being required for XEmacs
> compatibility. (XEmacs is still alive, if perhaps on life support.
> SXEmacs is very much alive.) The alternative suggested in the patch's
> `make-obsolete' form most assuredly won't work in XEmacs, yet hackers
> aren't warned about this there.
Which part wouldn't work in XEmacs?
> But the main thing I don't like about the patch is that it's a lot of
> work (for both of us), yet doesn't solve a single bug, and doesn't
> implement any new feature. The new `c-mode-common', which isn't a
> coherent entity, is going to cause problems (and hence take up more time)
> when somebody tries to derive directly from it. Possibly there will be
> other problems with the patch.
So you prefer copy&paste? OK, it's your mess to deal with after all.
Stefan
next prev parent reply other threads:[~2016-05-28 17:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 0:41 Reify the cc-mode-common into an actual parent mode Stefan Monnier
2016-05-28 11:30 ` Alan Mackenzie
2016-05-28 17:51 ` Stefan Monnier [this message]
2016-05-29 9:45 ` Alan Mackenzie
2016-05-29 14:53 ` Stefan Monnier
2016-05-28 18:08 ` Stefan Monnier
2016-05-29 10:00 ` Alan Mackenzie
2016-05-30 17:37 ` 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=jwvzirankh6.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=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).