unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Philipp <p.stephani2@gmail.com>
Cc: 29339@debbugs.gnu.org
Subject: bug#29339: 27.0.50; CC-mode doesn't know about .mm and .M suffixes for Objective-C++
Date: 17 Nov 2017 19:00:35 -0000	[thread overview]
Message-ID: <20171117190035.77279.qmail@mail.muc.de> (raw)
In-Reply-To: <mailman.3878.1510925890.27995.bug-gnu-emacs@gnu.org>

In article <mailman.3878.1510925890.27995.bug-gnu-emacs@gnu.org> you wrote:

> GCC uses .mm or .M for Objective-C++,
> cf. https://gcc.gnu.org/onlinedocs/gcc-7.2.0/gcc/Overall-Options.html.
> However, neither `auto-mode-alist' nor `cc-other-file-alist' contain
> these file extensions.

I don't think there's an Objective-C++ mode out there in the wild.  So
what existing mode should be used for *.mm and *.M?  Is that mode a good
enough fit to be able, in good conscience, to use it for Obj-C++?

> In GNU Emacs 27.0.50 (build 17, x86_64-pc-linux-gnu, GTK+ Version 3.10.8)
>  of 2017-11-17 built on localhost
> Repository revision: 345c7d9c7b84c0c03ef1d0f32e9e0f39029be44a
> Windowing system distributor 'The X.Org Foundation', version 11.0.11803000
> System Description:     Ubuntu 14.04.5 LTS

[ .... ]

-- 
Alan Mackenzie (Nuremberg, Germany).






  parent reply	other threads:[~2017-11-17 19:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-17 13:36 bug#29339: 27.0.50; CC-mode doesn't know about .mm and .M suffixes for Objective-C++ Philipp
     [not found] ` <mailman.3878.1510925890.27995.bug-gnu-emacs@gnu.org>
2017-11-17 19:00   ` Alan Mackenzie [this message]
2017-12-21 19:22     ` Philipp Stephani
2017-12-22 12:56       ` Alan Mackenzie
2017-12-22 16:50         ` Glenn Morris
2021-06-03 10:07           ` bug#2732: 23.0.91; Please add support " Lars Ingebrigtsen
2021-06-03 12:08             ` Philipp
2021-06-03 12:42               ` bug#29339: " Lars Ingebrigtsen
2021-06-03 12:45                 ` Lars Ingebrigtsen
2021-06-03 12:39             ` Alan Mackenzie

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=20171117190035.77279.qmail@mail.muc.de \
    --to=acm@muc.de \
    --cc=29339@debbugs.gnu.org \
    --cc=p.stephani2@gmail.com \
    /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).