unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] support a few of the new features of C++11 in syntax highlighting
Date: Wed, 14 May 2014 20:13:53 +0000	[thread overview]
Message-ID: <20140514201353.GA4125@acm.acm> (raw)
In-Reply-To: <87ha4wrle6.fsf@wanadoo.es>

Hello, Óscar.

On Mon, May 12, 2014 at 12:38:41AM +0200, Óscar Fuentes wrote:
> Alan Mackenzie <acm@muc.de> writes:

> >> So Alan noticed the patch, but the "no" still stands: the patch was not
> >> merged and there was no conclusion about it (except for Alan saying that
> >> he already implemented on the SF cc-mode some of the features mentioned
> >> on the patch and that he has no time for merging those changes into
> >> Emacs.)

> > These features are available in the c++11-0-1 branch of the CC Mode
> > repository at http://hg.code.sf.net/p/cc-mode/cc-mode, best downloaded by
> > prefixing the address with 'hg clone ', and appending it with a new
> > directory name.

> > As already stated, help in implementing further C++11 features would be
> > welcome.

> I would be more interested on helping to incorporate into Emacs the
> features already implemented on the SF repository.

> What can I do about that?

OK.  I suggest proceeding as follows.  First download the CC Mode
(Mercurial) repository, as detailed above.  Then get the diff between the
"default" branch (i.e. the trunk) and the c++11-0-1 branch for the files
cc-*.el:

    hg diff -r default:c++11-0-1 cc-*.el > foo.diff

.  Then (the hard part), disregarding the irrelevant diff hunks in that
file (e.g. changes in the copyright statement), apply the diffs to the
CC Mode files in the Emacs trunk.  This will likely involve a fair bit of
hand editing.  Please do this job very carefully - it would be a
knightmare to untangle if you were to make mistakes here.

Before committing this it would be best to test it using the regression
test suite in the directory ...../tests.  See the comments in the file
..../tests/000tests.el for instructions.  You'll need to move the entire
..../tests directory to under ..../lisp/progmodes (or set up appropriate
symbolic links) for this to work.

As a commit message, could you copy them from the CC Mode repository,
please.  All the commits in the c++-11-0-1 branch can be got reasonably
with:

    hg -v log -X .hgtags -b c++11-0-1

.  All the commits in default can similarly be got with

    hg -v log -X .hgtags -b default

.  Whatever changes are in c++-11-0-1 which aren't in default are the new
C++11 features.  They should form the basis of your commit message.

If you need any help, just email me.

Good luck!

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2014-05-14 20:13 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-25 12:51 [PATCH] support a few of the new features of C++11 in syntax highlighting Paul Pogonyshev
2014-01-25 19:58 ` Glenn Morris
2014-01-25 21:56   ` Stefan Monnier
2014-01-25 22:34     ` Daniel Colascione
2014-01-26  0:27       ` Glenn Morris
2014-01-26 12:29         ` Daniel Colascione
2014-01-26 15:21       ` Alan Mackenzie
2014-05-11  6:48 ` Václav Zeman
2014-05-11 16:00   ` Óscar Fuentes
2014-05-11 18:21     ` Glenn Morris
2014-05-11 20:19       ` Óscar Fuentes
2014-05-11 22:09         ` Alan Mackenzie
2014-05-11 22:38           ` Óscar Fuentes
2014-05-14 20:13             ` Alan Mackenzie [this message]
2014-05-14 21:20               ` Óscar Fuentes
2014-05-15  1:52               ` Stefan Monnier
2014-05-16 16:07                 ` Alan Mackenzie
2014-05-16 17:59                   ` Eli Zaretskii
2014-05-17  8:31                     ` Alan Mackenzie
2014-05-17  9:24                       ` Eli Zaretskii
2014-05-17 12:39                         ` Michael Albinus
2014-05-17 14:14                           ` Stefan Monnier
2014-05-17 14:24                             ` Michael Albinus
2014-05-17 15:10                               ` Stefan Monnier
2014-05-17 13:27                         ` Óscar Fuentes
2014-05-17 14:06                           ` Eli Zaretskii
2014-05-16 23:42                   ` Stefan Monnier
2014-05-17  4:17                     ` Richard Stallman
2014-05-17  9:03                       ` Alan Mackenzie
2014-05-17 15:45                         ` Richard Stallman
2014-05-19 15:46                         ` Barry Warsaw
2014-05-17  8:42                     ` Alan Mackenzie
2014-05-17 14:09                       ` Stefan Monnier
2014-11-16 17:36           ` Rüdiger Sonderfeld
2014-11-16 18:07             ` Óscar Fuentes
2014-11-18  2:41               ` Rüdiger Sonderfeld
2014-11-18  3:30                 ` Óscar Fuentes
2014-11-18 12:48                   ` Daniel Colascione
2014-11-18 14:47                     ` Óscar Fuentes
2014-11-18 16:36                       ` Rüdiger Sonderfeld
2014-11-18 17:13                         ` Daniel Colascione
2014-11-18 18:01                           ` Óscar Fuentes
2014-11-18 18:11                             ` Daniel Colascione
2014-11-18 18:33                               ` Óscar Fuentes
2014-11-18 12:49                 ` Daniel Colascione

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=20140514201353.GA4125@acm.acm \
    --to=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    --cc=ofv@wanadoo.es \
    /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).