[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CC Mode version number for Emacs 25.2

From: Alexander Shukaev
Subject: Re: CC Mode version number for Emacs 25.2
Date: Sat, 7 Jan 2017 23:02:10 +0100

On 12/22/2016 05:34 PM, Alan Mackenzie wrote:
Hello, Alexander.

On Thu, Dec 22, 2016 at 12:08:21AM +0100, Alexander Shukaev wrote:
On 12/20/2016 12:13 AM, Alexander Shukaev wrote:
On 12/18/2016 05:13 PM, Alan Mackenzie wrote:
Hello, Emacs.

The version of CC Mode within Emacs 25.1 is 5.33.  This is unfortunate,
since that version is at a much earlier stage of development than the
standalone CC Mode release 5.33.

This conflict in the use of "5.33" has led to some confusion amongst
people reporting bugs.

I would thus like to change the version number in Emacs 25.2 to
"5.32.99", to minimise further confusion.  I think it would be best to
make an entry about this in NEWS, too.  Incidentally, the actual code in
CC Mode in the Emacs 25 has not changed since the realease of 25.1.

Does anybody have any objections to this renumbering?


How to actually install this up-to-date version through 'package.el'?


Did my mail get lost or?

Sorry, just got a bit distracted by other things for a day or two.

CC Mode is not available through package.el.  There's either the version
in an Emacs release (which is frozen at pretest time, typically several
months before the release), or there's the stand alone version (which can
be any age) available from http://cc-mode.sourceforge.net/.  The latest
stand alone version, 5.33, was released in August 2016.

Alternatively, you can use the head of the VCS repository either at
savannah (for the entire Emacs version) or at sourceforge (for just CC

Hello Alan,

To me that looks like a major problem. It means that I have three options to keep track of your package:

1. Install it manually by copying corresponding '*.el' files into my Emacs configuration repository and shadow `load-path' on my own properly. 2. Make your repository to be a submodule of mine (what does not work for me since you are using Mercurial, while I use Git) and shadow `load-path' on my own properly.
3.  Use `el-get' to do that management for me.

All of these I find unacceptable: #1 smells like 90's (or earlier), #2 already mentioned, #3 requires another dependency that I don't want to deal with at the moment. All of that brings up a simple question: why such a widespread and useful package is not packaged on MELPA and other popular online archives?

Kind regards,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]