unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: /* */ style comments in C++ sources
Date: Thu, 25 May 2017 05:32:48 +0300	[thread overview]
Message-ID: <83wp95ll7z.fsf@gnu.org> (raw)
In-Reply-To: <20170524205316.GA6009@acm.fritz.box> (message from Alan Mackenzie on Wed, 24 May 2017 20:53:16 +0000)

> Date: Wed, 24 May 2017 20:53:16 +0000
> Cc: emacs-devel@gnu.org
> From: Alan Mackenzie <acm@muc.de>
> 
> What do you think of the following:
> 
> (i) There would be a new "CC Mode minor mode" with an interactive
> function called `c-toggle-comment-style', which would toggle a new buffer
> local variable, c-comment-style.  This variable could be set in local
> variables, or in .emacs in the same way as any other CC Mode buffer
> setting.
> (ii) `c-toggle-comment-style' would be bound to an unused CC Mode
> binding, possibly C-c C-k.
> (iii) I'm also thinking about putting it on C-c C-;, though terminal
> keyboards tend not to have C-; (mine doesn't (yet)).
> (iv) The major mode mode line entry, which currently looks something
> like "C/l" would be amended to "C/*l" or "C//l", with the obvious meaning.
> (v) The new buffer-local variable `c-comment-style' would influence all
> standard Emacs commands which create comments.
> 
> ?

Sounds good to me, thanks.



  parent reply	other threads:[~2017-05-25  2:32 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23 18:57 /* */ style comments in C++ sources Eli Zaretskii
2017-05-23 20:31 ` Alan Mackenzie
2017-05-24  0:02   ` Richard Stallman
2017-05-24 20:36     ` Sam Steingold
2017-05-24  2:27   ` Eli Zaretskii
2017-05-24 20:53     ` Alan Mackenzie
2017-05-25  1:51       ` Stefan Monnier
2017-05-25  2:32       ` Eli Zaretskii [this message]
2017-05-25 15:48         ` Alan Mackenzie
2017-05-25 16:59           ` Stefan Monnier
2017-05-25 17:44             ` Alan Mackenzie
2017-05-26  9:16           ` Alan Mackenzie
2017-06-15 21:10             ` Alan Mackenzie
2017-06-16  6:22               ` Eli Zaretskii
2017-06-16 11:50                 ` Alan Mackenzie
2017-06-16 12:40                   ` Alan Mackenzie
2017-06-16 13:33                     ` Eli Zaretskii
2017-06-16 13:22                   ` Eli Zaretskii
2017-06-16 13:37                     ` Stefan Monnier
2017-06-16 14:25                       ` Stefan Monnier
2017-06-16 16:15                         ` Eli Zaretskii
2017-06-16 18:45                           ` Stefan Monnier
2017-06-16 19:30                             ` Eli Zaretskii
2017-05-25  3:13       ` Herring, Davis
2017-05-25 16:00         ` Alan Mackenzie
2017-05-24 17:19   ` John Mastro
2017-05-24 18:10     ` Eli Zaretskii
2017-05-25  1:49       ` Stefan Monnier
2017-05-24  9:08 ` Dani Moncayo

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=83wp95ll7z.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=acm@muc.de \
    --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).