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: Thu, 01 May 2014 17:03:23 +0200 [thread overview]
Message-ID: <87ha59h77o.fsf@nl106-137-194.student.uu.se> (raw)
In-Reply-To: mailman.441.1398955214.1147.help-gnu-emacs@gnu.org
Drew Adams <drew.adams@oracle.com> writes:
> I already pointed out that M-; will nest. And that
> it will unnest, but only if the region contains only
> commented lines.
OK, you mean uncomment-region will uncomment this,
while M-; will comment it additionally?
;; code
code
Then, one has to wonder why the second line is included
in the region to begin with? I guess, if you use this
on big chunks of code with comments and code
interleaved, it might be useful.
>> > A DWIM command is often limited this way; it is a
>> > compromise.
>>
>> It doesn't have to be.
>
> It has to be. It is a guess wrt what any given user
> wants at any given time.
Yes, but from the users' perspective they know what
state gives what behaviour, so it is just an
alternative way (a better, often) to tell the computer
what to do. Or not having to do anything to still tell
the computer that, if the state is already ripe for
executing the command with a certain behaviour in
mind. And if the DWIM command is good, that should
happen more often than not.
--
underground experts united:
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2014-05-01 15: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
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 [this message]
[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=87ha59h77o.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).