The title says it all really.

Version 2.0.6 has been released. Hopefully Arch, MacPorts, Debian, Fedora, etc. will look to package this.

Alternatively for Emacs 24+ folk use packaging, put MELPA in the path
and get the latest version from GitHub automatically. That's
2.0.7-SNAPSHOT now :-)

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

On Monday, 22 July 2013 at 10:40:05 UTC, Russel Winder wrote:
> The title says it all really.
>
> Version 2.0.6 has been released. Hopefully Arch, MacPorts, Debian,
> Fedora, etc. will look to package this.
>
> Alternatively for Emacs 24+ folk use packaging, put MELPA in the path
> and get the latest version from GitHub automatically. That's
> 2.0.7-SNAPSHOT now :-)
> 

Thanks very much for this.

On 7/22/2013 3:39 AM, Russel Winder wrote:
> The title says it all really.

Need linky!

On Tuesday, 23 July 2013 at 21:59:21 UTC, Walter Bright wrote:
> On 7/22/2013 3:39 AM, Russel Winder wrote:
>> The title says it all really.
>
> Need linky!

https://github.com/Emacs-D-Mode-Maintainers/Emacs-D-Mode

Walter,

On Tue, 2013-07-23 at 14:59 -0700, Walter Bright wrote:
> On 7/22/2013 3:39 AM, Russel Winder wrote:
> > The title says it all really.
> 
> Need linky!

Did John Colvin's reply suffice?

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

Russel Winder <russel@winder.org.uk> writes:

> The title says it all really.
>
> Version 2.0.6 has been released. Hopefully Arch, MacPorts, Debian, Fedora, etc. will look to package this.
>
> Alternatively for Emacs 24+ folk use packaging, put MELPA in the path and get the latest version from GitHub automatically. That's 2.0.7-SNAPSHOT now :-)

There are a few things not fontified correctly in my Emacs (24.3.50.1 git master of 2013-6-12).  I just checked with the latest github version and they are still not fixed:

* The first member variable or function name under a protection level
  label (public/protected/private etc.) is not fontified.

* Types with namespaces (.) or are template instances(!) are not
  fontified.

* auto/immutable variables are not fontified with the correct face. They
  should be in variable face but are displaced in type name face
  instead.

I have a hacked version in my site-lisp directory that fixes most of these issues for me but because I'm not familiar with the CC-mode codebase my solutions are very rough and hacky.

-- 
finalpatch

On Wed, 2013-07-31 at 23:01 +1000, finalpatch wrote:
[…]
> There are a few things not fontified correctly in my Emacs (24.3.50.1 git master of 2013-6-12).  I just checked with the latest github version and they are still not fixed:
> 
> * The first member variable or function name under a protection level
>   label (public/protected/private etc.) is not fontified.
> 
> * Types with namespaces (.) or are template instances(!) are not
>   fontified.
> 
> * auto/immutable variables are not fontified with the correct face. They
>   should be in variable face but are displaced in type name face
>   instead.
> 
> I have a hacked version in my site-lisp directory that fixes most of these issues for me but because I'm not familiar with the CC-mode codebase my solutions are very rough and hacky.

The way to progress this is for you to to clone the GitHub repository on GitHub, clone it locally to your machines, create a feature branch with your proposed changes, push them to your GitHub clone and then submit a pull request via GitHub.  I and others can then try things out and see if the pull request can be merged into master.

The one thing that still worries me about all the E-Lisp stuff – no unit tests :-(

Thanks.
-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

Hi Russel,

I'm not proposing my changes to be merged into master because I know they are merely workarounds rather than proper fixes (eg. font-lock-add-keywords).

On Thursday, 1 August 2013 at 08:07:28 UTC, Russel Winder wrote:
>
> The way to progress this is for you to to clone the GitHub repository on
> GitHub, clone it locally to your machines, create a feature branch with
> your proposed changes, push them to your GitHub clone and then submit a
> pull request via GitHub.  I and others can then try things out and see
> if the pull request can be merged into master.
>
> The one thing that still worries me about all the E-Lisp stuff – no unit
> tests :-(
>
> Thanks.

On Thu, 2013-08-01 at 16:32 +0200, finalpatch wrote:
> Hi Russel,
> 
> I'm not proposing my changes to be merged into master because I know they are merely workarounds rather than proper fixes (eg. font-lock-add-keywords).

Development on this is event driven. Having an event of a hack fix, may lead to investigation and thence a proper fix!

Basically it would be good to see something that solves the problem as input to trying to find the "proper solution".

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

On Thursday, 1 August 2013 at 19:01:19 UTC, Russel Winder wrote:
> On Thu, 2013-08-01 at 16:32 +0200, finalpatch wrote:
>> Hi Russel,
>> 
>> I'm not proposing my changes to be merged into master because I know they are merely workarounds rather than proper fixes (eg. font-lock-add-keywords).
>
> Development on this is event driven. Having an event of a hack fix, may
> lead to investigation and thence a proper fix!
>
> Basically it would be good to see something that solves the problem as
> input to trying to find the "proper solution".

I have opened a pull request on github.

The changes are:

* Fix auto/immutable variable face
* Move 'template' to c-class-decl-kwds
* Add imenu support
* Fix fontification of the first declariation after a protection level label