unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Dale Snell <ddsnell@frontier.com>
To: help-gnu-emacs@gnu.org
Subject: Re: one key-press to comment out lines of code?
Date: Wed, 30 Apr 2014 09:27:49 -0700	[thread overview]
Message-ID: <20140430092749.4834bb92@zothique> (raw)
In-Reply-To: <87fvku94ms.fsf@skimble.plus.com>

On Wed, 30 Apr 2014 17:14:03 +0100
Sharon Kimble <boudiccas@skimble.plus.com> wrote:

> Whilst I'm still learning emacs and gnus I'm constantly adding code
> to my "setup-testbed.el" file, and then finding later that it doesn't
> do what its expected to do, or I don't like the outcome, so I then
> comment it out. Currently, I'm doing it laboriously by hand, but is
> it possible to highlight it and then with one key-press insert ";" in
> front of each and every line of the code please?
> 
> I haven't seen this ability anywhere, but being able to do it would
> make things a whole lot easier for me, so, can it be done please
> folks?

Well, it's not precisely one keypress, but here's what I do:

Set point and mark to define the region.  Then do

    C-x r t RET ; SPC RET

That should do it.  If you don't like the space, you can leave it
out.  I like a little whitespace between my comment symbols and
the program text.

Hope this helps.

--Dale

--
"Text processing has made it possible to right-justify any idea, even
one which cannot be justified on any other grounds."
		-- J. Finnegan, USC.



  parent reply	other threads:[~2014-04-30 16:27 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 [this message]
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
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=20140430092749.4834bb92@zothique \
    --to=ddsnell@frontier.com \
    --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).