From: Barry Warsaw <barry@python.org>
To: emacs-devel@gnu.org
Subject: Re: [PATCH] support a few of the new features of C++11 in syntax highlighting
Date: Mon, 19 May 2014 11:46:11 -0400 [thread overview]
Message-ID: <20140519114611.7e053a2c@anarchist.wooz.org> (raw)
In-Reply-To: 20140517090321.GC3398@acm.acm
[-- Attachment #1: Type: text/plain, Size: 762 bytes --]
On May 17, 2014, at 09:03 AM, Alan Mackenzie wrote:
>Presumably Barry Warsaw. At the time (1992), I'm pretty sure he was
>an XEmacs user, so would naturally want to support that platform too.
Gosh, 22 years is ancient history. I think this was even before the XEmacs
name. It was probably still called Lucid Emacs! Back then, SourceForge
seemed like the best public code hosting site available. I don't remember,
but we might have even used CVS at the time. ;)
I switched back to GNU Emacs in 2008.
That's not to say that XEmacs support should be dropped. I personally don't
care about it much any more, but other people do, and I think we should
respect the current CC Mode maintainer's opinion on matters like this.
Cheers,
-Barry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-05-19 15:46 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
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 [this message]
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=20140519114611.7e053a2c@anarchist.wooz.org \
--to=barry@python.org \
--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).