From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.devel Subject: Re: Include modern-cpp-font-lock into GNU Emacs Date: Sat, 11 Aug 2018 14:51:24 +0000 Message-ID: <20180811145124.GA4992@ACM> References: <53cad8eb-9bf1-e2d3-90cf-10a9874bf69b@lud.cc> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: blaine.gmane.org 1533999301 802 195.159.176.226 (11 Aug 2018 14:55:01 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 11 Aug 2018 14:55:01 +0000 (UTC) User-Agent: Mutt/1.10.1 (2018-07-13) Cc: emacs-devel@gnu.org To: Ludwig PACIFICI Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Aug 11 16:54:57 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1foVI6-0008WG-Nv for ged-emacs-devel@m.gmane.org; Sat, 11 Aug 2018 16:54:54 +0200 Original-Received: from localhost ([::1]:60431 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1foVKD-0000Cn-8d for ged-emacs-devel@m.gmane.org; Sat, 11 Aug 2018 10:57:05 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50693) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1foVK2-0000Ch-VQ for emacs-devel@gnu.org; Sat, 11 Aug 2018 10:56:56 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1foVJz-0008Hu-Ro for emacs-devel@gnu.org; Sat, 11 Aug 2018 10:56:55 -0400 Original-Received: from colin.muc.de ([193.149.48.1]:38544 helo=mail.muc.de) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1foVJz-0008ES-Le for emacs-devel@gnu.org; Sat, 11 Aug 2018 10:56:51 -0400 Original-Received: (qmail 51205 invoked by uid 3782); 11 Aug 2018 14:56:48 -0000 Original-Received: from acm.muc.de (p5B147B54.dip0.t-ipconnect.de [91.20.123.84]) by colin.muc.de (tmda-ofmipd) with ESMTP; Sat, 11 Aug 2018 16:56:47 +0200 Original-Received: (qmail 9305 invoked by uid 1000); 11 Aug 2018 14:51:24 -0000 Content-Disposition: inline In-Reply-To: <53cad8eb-9bf1-e2d3-90cf-10a9874bf69b@lud.cc> X-Delivery-Agent: TMDA/1.1.12 (Macallan) X-Primary-Address: acm@muc.de X-detected-operating-system: by eggs.gnu.org: FreeBSD 9.x [fuzzy] X-Received-From: 193.149.48.1 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:228407 Archived-At: 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).