all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: "Mattias Engdegård" <mattiase@acm.org>,
	"Lars Ingebrigtsen" <larsi@gnus.org>,
	44554@debbugs.gnu.org, "Vladimir Nikishkin" <lockywolf@gmail.com>,
	"Richard Stallman" <rms@gnu.org>
Subject: bug#44554: 27.1; Feature request: SRFI-62 style comments for Emacs Lisp.
Date: Fri, 13 Nov 2020 14:07:46 +0000	[thread overview]
Message-ID: <xjfy2j5cpu5.fsf@sdf.org> (raw)
In-Reply-To: <CADwFkmnq2MkYqzX-97ur7tp08+EorYDsWgJoidRXgcURb7u4AA@mail.gmail.com> (Stefan Kangas's message of "Fri, 13 Nov 2020 05:47:08 -0800")

Stefan Kangas <stefankangas@gmail.com> writes:

> Andrea Corallo <akrl@sdf.org> writes:
>
>> That said I believe `comment-dwim' solves already this problem to a good
>> degree for me.
>>
>> given:
>>
>> (foo (bar))
>>
>> having as a region '(bar)' M-; produces
>>
>> (foo ;; (bar)
>>      )
>
> Indeed.
>
> What's less fun is when you have to back the change out, or when you
> want to incrementally comment out a nested sexp.  It works well, but
> it's a wee bit fiddly.
>
> For example, given:
>
> (foo (bar ...
>           (baz ...)))
>
> With `comment-dwim', I might get something like:
>
> (foo ;; (bar ...
>      ;;      ;; (baz ...)
>      ;;      )
>      )
>
> This would be more convenient:
>
> (foo #;(bar ...
>           #;(baz ...)))

Agree, that's one of the reasons why I agree would be nice to have ;)

As typically we do not commit commented code is no big deal as we
probably (at least I) revert the unnecessary diff hunks, but yeah would
be an improvement.  Also uncommenting would put the code in the initial
state instead of leaving unnecessary newlines.

  Andrea





  reply	other threads:[~2020-11-13 14:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 14:04 bug#44554: 27.1; Feature request: SRFI-62 style comments for Emacs Lisp Vladimir Nikishkin
2020-11-10 14:57 ` Lars Ingebrigtsen
2020-11-10 15:11   ` Vladimir Nikishkin
2020-11-10 17:17   ` Drew Adams
2020-11-13 18:32     ` João Távora
2020-11-10 19:31   ` Jean Louis
2020-11-11  5:40     ` Richard Stallman
2020-11-11  5:48       ` Jean Louis
2020-11-11  8:18         ` Vladimir Nikishkin
2020-11-11  8:25           ` Jean Louis
2020-11-11 14:18             ` Vladimir Nikishkin
2020-11-12 23:55             ` Eduardo Ochs
2020-11-11  8:29           ` Andreas Schwab
2020-11-11 22:50             ` Jose A. Ortega Ruiz
2020-11-10 17:17 ` Francesco Potortì
2020-11-10 23:18   ` Jose A. Ortega Ruiz
2020-11-11 16:10 ` Mattias Engdegård
2020-11-11 16:14   ` Vladimir Nikishkin
2020-11-11 16:25     ` Mattias Engdegård
2020-11-12 12:50       ` Lars Ingebrigtsen
2020-11-12 18:16         ` Drew Adams
2020-11-12 20:11           ` Juri Linkov
2020-11-12 20:44             ` Drew Adams
2020-11-13  0:38         ` Stefan Kangas
2020-11-13 13:24           ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-13 13:47             ` Stefan Kangas
2020-11-13 14:07               ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2020-11-13 21:03           ` Tassilo Horn

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=xjfy2j5cpu5.fsf@sdf.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=44554@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=larsi@gnus.org \
    --cc=lockywolf@gmail.com \
    --cc=mattiase@acm.org \
    --cc=rms@gnu.org \
    --cc=stefankangas@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 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.