unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: one key-press to comment out lines of code?
Date: Wed, 30 Apr 2014 21:03:54 +0200	[thread overview]
Message-ID: <874n1ak5b9.fsf@nl106-137-194.student.uu.se> (raw)
In-Reply-To: mailman.391.1398874951.1147.help-gnu-emacs@gnu.org

Drew Adams <drew.adams@oracle.com> writes:

> Others will no doubt tell you to use `M-;'
> (`comment-dwim') after selecting the text.

Easy to remember! - as the Lisp comment char (the
initiator for one-line comments).

> I prefer to use `comment-region', which I bind to
> `C-x ;'.

Why not use M-; for that as well? C-SPC, move point,
M-; last.

> To uncomment, provide a plain prefix arg (`C-u'):
> `C-u C-x ;'.  To comment using N comment chars, use a
> numeric prefix arg: `C-3 C-x ;'.  (And you can use
> that to nest commented text.)

Yeah, but again, I think it is much simpler to C-SPC,
move point, and M-; (if the region is commented) to
uncomment.

So for all three cases: M-;.

Note that in all programming modes it is still M-; - so
it is not M-// in C++, M-% in LaTeX, etc., or anything
like that.

Even if there is no commenting style defined, hit M-;
and Emacs will ask you what char to use. (Though if
that happens a lot, you should probably configure it
for a file extension, a hash bang or something like
that.)

-- 
underground experts united:
http://user.it.uu.se/~embe8573


  parent reply	other threads:[~2014-04-30 19:03 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-30 16:14 one key-press to comment out lines of code? Sharon Kimble
2014-04-30 16:22 ` Drew Adams
2014-04-30 17:09   ` Michael Heerdegen
2014-04-30 17:18     ` Michael Heerdegen
2014-04-30 16:27 ` Dale Snell
2014-04-30 17:38 ` Andreas Röhler
2014-04-30 19:02 ` Stefan Monnier
     [not found] ` <mailman.391.1398874951.1147.help-gnu-emacs@gnu.org>
2014-04-30 19:03   ` Emanuel Berg [this message]
2014-04-30 20:54     ` Drew Adams
2014-04-30 21:06       ` Drew Adams
     [not found]     ` <mailman.414.1398891311.1147.help-gnu-emacs@gnu.org>
2014-05-01 13:54       ` Emanuel Berg
2014-05-01 14:39         ` Drew Adams
     [not found]         ` <mailman.441.1398955214.1147.help-gnu-emacs@gnu.org>
2014-05-01 15:03           ` Emanuel Berg
     [not found] ` <mailman.392.1398875301.1147.help-gnu-emacs@gnu.org>
2014-04-30 19:10   ` Emanuel Berg
2014-04-30 20:09     ` Joost Kremers
2014-05-01 14:15       ` Emanuel Berg
2014-05-01 14:31         ` Joost Kremers
2014-04-30 21:12     ` Dale Snell
     [not found]     ` <mailman.417.1398892388.1147.help-gnu-emacs@gnu.org>
2014-05-01 14:05       ` Emanuel Berg
2014-05-01 22:54         ` Dale Snell
     [not found]         ` <mailman.469.1398984898.1147.help-gnu-emacs@gnu.org>
2014-05-01 23:42           ` Emanuel Berg
2014-05-02  0:11             ` Joost Kremers
2014-05-02  1:23               ` Emanuel Berg
2014-05-03  2:01               ` Emanuel Berg
2014-05-03  2:43                 ` Emanuel Berg
2014-05-02 17:42             ` Dale Snell
     [not found]             ` <mailman.520.1399052563.1147.help-gnu-emacs@gnu.org>
2014-05-02 19:59               ` Emanuel Berg

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=874n1ak5b9.fsf@nl106-137-194.student.uu.se \
    --to=embe8573@student.uu.se \
    --cc=help-gnu-emacs@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.
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).