From: "Wedler, Christoph" <christoph.wedler@sap.com>
To: John Wiegley <jwiegley@gmail.com>,
Stephen Leake <stephen_leake@stephe-leake.org>
Cc: jan <rtm443x@googlemail.com>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: Obsolete antlr-mode shipped with emacs 24.5.1
Date: Mon, 23 Nov 2015 17:21:15 +0000 [thread overview]
Message-ID: <F9C2521BBF380A4A97379009991555E699357661@DEWDFEMB17C.global.corp.sap> (raw)
In-Reply-To: <m24mgckbfm.fsf@newartisans.com>
>>>>>> Stephen Leake <stephen_leake@stephe-leake.org> writes:
>>>> He asked me to post here and ask whether antlr-mode could be updated then?
>>> It would go onto master, once it's ready.
>> Or Gnu ELPA, more likely
> I'd prefer that, yes, except that it's in core already, and we haven't yet
> made the choice to move things around.
Gnu ELPA or core Emacs is both fine with me.
There is one question if we remove it from core Emacs: how about the
entry ".g" in speedbar-supported-extension-expressions?
1. Keep it even if there is no core major-mode anymore which supports it.
A bit strange, but not really an issue.
2. Remove it. Then antlr-mode has to add the entry, BUT: it is a
customizable variable and another variable (speedbar-file-regexp)
depends on it on load time -> I am a bit reluctant to do that...
- Christoph
P.S. Next week there should be a version of antlr-mode which is also
"custom-stable" enough... (in terms of usage, the newest 3.1.0 should be
more stable than the version 2.2.3 shipped with Emacs)
next prev parent reply other threads:[~2015-11-23 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 12:11 Obsolete antlr-mode shipped with emacs 24.5.1 jan
2015-11-23 13:56 ` John Wiegley
2015-11-23 14:46 ` Stephen Leake
2015-11-23 15:00 ` John Wiegley
2015-11-23 17:21 ` Wedler, Christoph [this message]
2015-11-23 17:44 ` John Wiegley
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F9C2521BBF380A4A97379009991555E699357661@DEWDFEMB17C.global.corp.sap \
--to=christoph.wedler@sap.com \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@gmail.com \
--cc=rtm443x@googlemail.com \
--cc=stephen_leake@stephe-leake.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.