unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: Feature request: CMake-mode
Date: Fri, 02 Oct 2020 04:49:34 +0200	[thread overview]
Message-ID: <877ds9fikh.fsf@telefonica.net> (raw)
In-Reply-To: 20201002005325.xew6i3ypgdmnon5j@Ergus

Ergus <spacibba@aol.com> writes:

>>> There is a package in melpa which is very poorly maintained by the
>>> cmake community.
>>>
>>> https://melpa.org/packages/cmake-mode-20190710.1319.el
>>> https://github.com/Kitware/CMake/blob/master/Auxiliary/cmake-mode.el
>>
>>And you think that we would do better? :-)
>>
> The package seems not really very maintained.

[snip]

>>> Could we consider to add a native cmake mode to vanilla or contact the
>>> Kitware people to add this one to elpa? Or in the worst case to change
>>> the name of their package in order to release the name and add a GPL
>>> versioned one to elpa?
>>
>>CMake releases new versions quite often, so an elpa package (not to
>>mention a vanilla one) would soon be outdated unless someone (TM)
>>commits to keeping it up to date.
>>
> That's true. But actually the Kitware file supports only the most basic
> keywords. Most of the new features, and syntax are not included there
> any way.

So are you requesting to include Kitware's incomplete cmake-mode.el into
Elpa/Emacs or to develop a new mode (possibly based on Kitware's)? If
people is not contributing enough to Kitware's mode what makes you think
that once included into Emacs (with its added requirements about signing
papers, etc) it would be better?




      reply	other threads:[~2020-10-02  2:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87mu15tw3d.fsf.ref@Ergus.i-did-not-set--mail-host-address--so-tickle-me>
2020-10-01 22:33 ` Feature request: CMake-mode Ergus
2020-10-02  0:25   ` Óscar Fuentes
2020-10-02  0:53     ` Ergus
2020-10-02  2:49       ` Óscar Fuentes [this message]

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=877ds9fikh.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --cc=emacs-devel@gnu.org \
    /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).