all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Emanuel Berg <embe8573@student.uu.se>, help-gnu-emacs@gnu.org
Subject: RE: one key-press to comment out lines of code?
Date: Thu, 1 May 2014 07:39:51 -0700 (PDT)	[thread overview]
Message-ID: <fe66c992-7b01-467e-ac85-6c4a1bdb1588@default> (raw)
In-Reply-To: <87ha59ioyw.fsf@nl106-137-194.student.uu.se>

> > `M-;' cannot uncomment the commented lines in the
> > region when there are also uncommented lines.
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
> Alright, nested comments! I never did that so I never
> thought about it. But what I can see, M-; works for
> those as well:
> 
> ;; ;; commented-out comment
> into
> ;; commented-out comment

See above: "^^^^^".  I already pointed out that M-; will nest.
And that it will unnest, but only if the region contains only
commented lines.

> and
> ;; (message "done") ; redundant comment
> into
> (message "done") ; redundant comment
> as well as "mulit-;" comments:
> ;;;; IMPORTANT
> into
> IMPORTANT

See above - same story.  And my previous mails about this.
And the doc.  And witness the behavior.

> I don't really comment-out code - but when I do, M-;
> always worked.
> 
> What are the use-cases where M-; doesn't work? Perhaps
> that could be solved somehow - depends on how varied,
> and how advanced, those situations are, of course.

See what I wrote previously.  Or look at the doc of
`comment-dwim' vs `comment-region'.  Or experiment and see.

It's not about "solving" `comment-dwim's differences.  They
are different on purpose, presumably.  It is a compromise.
If it works well enough for what you want, great.

> > 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.

Compromises can be good or bad, handy or not, depending on
the algorithm, the user, and the situation.  All commands
are compromises, of course.  Some give the user more control.

`comment-dwim' doesn't give you the `comment-region' behavior
and control.  In my case that means it doesn't give me what
I want.  YMMV.



  reply	other threads:[~2014-05-01 14:39 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 [this message]
     [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fe66c992-7b01-467e-ac85-6c4a1bdb1588@default \
    --to=drew.adams@oracle.com \
    --cc=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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.