From: Paul Eggert <eggert@cs.ucla.edu>
To: John Wiegley <johnw@gnu.org>
Cc: Alan Mackenzie <acm@muc.de>, 22884@debbugs.gnu.org
Subject: bug#22884: 25.0.92; C/l mode editing takes waaaayy too long
Date: Wed, 9 Mar 2016 01:37:45 -0800 [thread overview]
Message-ID: <56DFEEE9.2030603@cs.ucla.edu> (raw)
In-Reply-To: <m28u1s0zl1.fsf@newartisans.com>
John Wiegley wrote:
> Coq supports (* foo (* bar *) *), in the same way that C does with /* */.
It's not the same way as C, since C comments do not nest.
> Was there something more you wanted to know?
It's up to Alan, but I suppose Alan may want simple directions to try out nested
comments in Coq, for someone who does not know Coq at all. E.g., what should
the file name and contents be, and what emacs -Q keystrokes should one type to
illustrate how nested comments work.
next prev parent reply other threads:[~2016-03-09 9:37 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 18:08 bug#22884: 25.0.92; C/l mode editing takes waaaayy too long Paul Eggert
2016-03-03 12:49 ` Alan Mackenzie
2016-03-03 17:54 ` Paul Eggert
2016-03-03 19:23 ` Alan Mackenzie
2016-03-03 20:38 ` Eli Zaretskii
2016-03-03 21:57 ` Paul Eggert
2016-03-03 22:59 ` Alan Mackenzie
2016-03-03 20:51 ` Eli Zaretskii
2016-03-03 23:44 ` Paul Eggert
2016-03-04 14:47 ` Alan Mackenzie
2016-03-04 20:32 ` Paul Eggert
2016-03-04 21:08 ` Alan Mackenzie
2016-03-13 10:03 ` Alan Mackenzie
2016-03-08 14:02 ` Alan Mackenzie
2016-03-09 8:25 ` Paul Eggert
2016-03-09 9:28 ` John Wiegley
2016-03-09 9:37 ` Paul Eggert [this message]
2016-03-09 21:30 ` John Wiegley
2016-03-09 10:56 ` Alan Mackenzie
2016-03-09 14:44 ` Drew Adams
2016-03-09 17:04 ` Alan Mackenzie
2016-03-09 17:14 ` Drew Adams
2016-03-03 20:40 ` Eli Zaretskii
2016-03-03 22:27 ` Alan Mackenzie
2016-03-03 23:18 ` Alan Mackenzie
2016-03-04 8:32 ` Eli Zaretskii
2016-03-04 9:37 ` Alan Mackenzie
2016-03-15 3:07 ` Stefan Monnier
2016-05-08 23:10 ` Dmitry Gutov
2016-05-13 19:35 ` Paul Eggert
2016-05-13 20:37 ` Glenn Morris
2016-05-13 21:09 ` Paul Eggert
2022-04-28 11:22 ` Lars Ingebrigtsen
2022-04-28 19:35 ` Paul Eggert
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=56DFEEE9.2030603@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=22884@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=johnw@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).