From: Robert Thorpe <rt@robertthorpeconsulting.com>
To: Davis Herring <herring@lanl.gov>
Cc: emacs-devel@gnu.org, bric@flight.us, l26wang@gmail.com
Subject: Re: awesome feature (yet to be added?)
Date: Tue, 06 May 2014 23:27:11 +0100 [thread overview]
Message-ID: <87oazaczls.fsf@robertthorpeconsulting.com> (raw)
In-Reply-To: <53684CB6.1050601@lanl.gov> (message from Davis Herring on Mon, 05 May 2014 20:45:10 -0600)
Davis Herring <herring@lanl.gov> writes:
>> Judging by the uptake. We are the only two to think this is useful. :)
>
> I thought about implementing `invert-comment' a few years ago, but I
> wasn't sure what to do about code like this:
>
> /* old_implementation_prepare (); */
> /* old_implementation_go (); */
Here's an alternative approach.
Dale Snell pointed out that this can be done with rectangle commands.
Give your commented code a name. Mark region with the mark and point in
the first column. Then do
C-x r t ;; foo: RET
The region will look like
;; foo: some code ();
;; foo: some more code ();
You can do the same for other experiments that are commented out. Then
later on you can enable them by using
M-% ;; foo: RET RET
And you can put a ! at the end of that if you like. I know this doesn't
solve all the problems discussed.
BR,
Robert Thorpe
next prev parent reply other threads:[~2014-05-06 22:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-03 18:47 awesome feature (yet to be added?) Bric
2014-05-04 1:23 ` Bric
2014-05-04 11:12 ` Stephen Berman
2014-05-04 18:33 ` Andreas Röhler
2014-05-06 2:32 ` Le Wang
2014-05-06 2:45 ` Davis Herring
2014-05-06 8:19 ` Stephen J. Turnbull
2014-05-06 22:27 ` Robert Thorpe [this message]
2014-05-30 21:35 ` Thorsten Jolitz
2014-05-31 1:30 ` Stefan Monnier
2014-05-31 10:46 ` Thorsten Jolitz
2014-06-09 11:01 ` Thorsten Jolitz
2014-06-09 15:30 ` Stefan Monnier
2014-05-31 6:26 ` Andreas Röhler
2014-05-31 10:52 ` Thorsten Jolitz
2014-05-31 17:20 ` Andreas Röhler
2014-05-31 20:04 ` Thorsten Jolitz
2014-06-01 7:00 ` Andreas Röhler
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=87oazaczls.fsf@robertthorpeconsulting.com \
--to=rt@robertthorpeconsulting.com \
--cc=bric@flight.us \
--cc=emacs-devel@gnu.org \
--cc=herring@lanl.gov \
--cc=l26wang@gmail.com \
/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).