From: Ludwig PACIFICI <ludwig@lud.cc>
To: acm@muc.de
Cc: emacs-devel@gnu.org
Subject: Re: Include modern-cpp-font-lock into GNU Emacs
Date: Sun, 19 Aug 2018 12:16:37 +0100 [thread overview]
Message-ID: <4e10dfa3-4793-f680-8a85-78a489884cad@lud.cc> (raw)
In-Reply-To: <20180811145124.GA4992@ACM>
Hello Alan,
Thank you for your reply.
> In what respects is this package an improvement over the fontification
> in standard C++ Mode?
About two years ago, when I was writing C++ programs, I wanted to have a
quick fix for the missing fontification. It is not an improvement from
standard C++ mode, but a quicker way to get the font lock up to date.
> Do you have an up to date diff betweeen m-c-f-l.el and C++ Mode - things
> that m-c-f-l handles, but C++ Mode doesn't?
No. In my opinion, I should do that diff, and, if any, contact you via
cc-mode project to reduce the gap?
> I think I would prefer to integrate missing font locking into CC Mode,
> rather than introducing a new ad-hoc package which doesn't fit well with
> CC Mode. But I do accept your comment about the rate of release of C++
> Mode.
I believe the issue is broader than m-c-f-l and cc-mode. The difference
between an Emacs release cycle (where Emacs provides a built-in support
for some languages, like cc-mode, python, ruby-mode, etc.) and the
release cycle of a language can lead to a long delay to get things right
(such as font locking). Having the language support delivered via a
package manager makes the updates less dependent of release cycles.
Ludwig
next prev parent reply other threads:[~2018-08-19 11:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 20:24 Include modern-cpp-font-lock into GNU Emacs Ludwig PACIFICI
2018-08-11 14:51 ` Alan Mackenzie
2018-08-12 0:22 ` Stefan Monnier
2018-08-19 11:16 ` Ludwig PACIFICI [this message]
2018-08-19 12:31 ` Stefan Monnier
2018-08-20 3:03 ` Richard Stallman
2018-08-20 8:38 ` Andy Moreton
2018-08-20 9:28 ` Jostein Kjønigsen
2018-08-20 10:51 ` Noam Postavsky
2018-08-20 11:28 ` Andy Moreton
2018-08-20 17:54 ` Jostein Kjønigsen
2018-08-20 19:45 ` Michael Albinus
2018-08-22 12:46 ` Noam Postavsky
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=4e10dfa3-4793-f680-8a85-78a489884cad@lud.cc \
--to=ludwig@lud.cc \
--cc=acm@muc.de \
--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 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.