From: Alan Mackenzie <acm@muc.de>
To: Ludwig PACIFICI <ludwig@lud.cc>
Cc: emacs-devel@gnu.org
Subject: Re: Include modern-cpp-font-lock into GNU Emacs
Date: Sat, 11 Aug 2018 14:51:24 +0000 [thread overview]
Message-ID: <20180811145124.GA4992@ACM> (raw)
In-Reply-To: <53cad8eb-9bf1-e2d3-90cf-10a9874bf69b@lud.cc>
Hello, Ludwig.
On Mon, Aug 06, 2018 at 21:24:51 +0100, Ludwig PACIFICI wrote:
> Hello emacs-devel
> After a reddit post[1], I'd like to discuss with you the possibility to
> integrate modern-cpp-font-lock into GNU Emacs.
> modern-cpp-font-lock[2] is a font lock improvement for recent version of
> C++ - so far, up to C++17. It can be seen as an add-on of the c++-mode
> (part of CC Mode).
In what respects is this package an improvement over the fontification
in standard C++ Mode?
> I published this package to improve the C++ support in Emacs. The
> release cycle of C++ and Emacs are slow. Especially if not in synced, it
> can lead to a long time with lack of support for the language. Melpa[3]
> is a good place to release modern-cpp-font-lock, because it enables
> quicker release cycles.
I've briefly skimmed modern-cpp-font-lock.el. It seems there is a _lot_
of duplication with C++ Mode - m-c-f-l attempts to fontify all C++
keywords, even though nearly all will be already fontified by C++ Mode;
raw strings are now handled by C++ Mode; nullptr, false, true are also
handled by C++ Mode; and so on.
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? I suspect that difference
will be small to medium, rather than large.
> Let me know what are your opinions.
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.
> Best regards
> Ludwig
> [1]:
> https://www.reddit.com/r/emacs/comments/94j39z/modern_c_font_lock_in_emacs/
> [2]: https://github.com/ludwigpacifici/modern-cpp-font-lock
> [3]: https://melpa.org/#/modern-cpp-font-lock
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2018-08-11 14:51 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 [this message]
2018-08-12 0:22 ` Stefan Monnier
2018-08-19 11:16 ` Ludwig PACIFICI
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
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=20180811145124.GA4992@ACM \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=ludwig@lud.cc \
/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).