unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: New comment-sexp command and key bind
Date: Fri, 21 Aug 2015 15:21:29 +0100	[thread overview]
Message-ID: <CAAdUY-JONUVY=GHWhVtJpGqZPTVWusXw-rMNcs8RAjhiZg9m-A@mail.gmail.com> (raw)
In-Reply-To: <jwv4mjs6ag1.fsf-monnier+emacs@gnu.org>

2015-08-21 14:31 GMT+01:00 Stefan Monnier <monnier@iro.umontreal.ca>:
>> (defun uncomment-sexp (&optional n)
>
> Clearly, this is the more important part, since C-M-SPC M-; does the
> trick for the commenting part.
>
> I think I like part of the idea, but being limited to uncommenting is
> rather frustrating.

Just to be clear. It's fine if the commented has multiple line even
with empty lines in the middle. The only problem is if there's
uncommented code in between some of the commented lines. In that case
I'm unsure what the sane behavior would even be.

> It's reasonably frequent to want to
> navigate/manipulate a sexp that spans several comments, and uncommenting
> it is not even the most common operation for me.
>
> So I'd be more interested in a way to make C-M-SPC, C-M-f and friends
> deal "correctly" with such "sexps that span several comments".

I think I've heard that smartparens does that. That is, if point is
inside a comment it deals with commented sexps as if they were
uncommented for all intents and purposes. But don't quote me on that.
=P



  reply	other threads:[~2015-08-21 14:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21 11:11 New comment-sexp command and key bind Artur Malabarba
2015-08-21 11:31 ` João Távora
2015-08-21 12:24   ` Artur Malabarba
2015-08-21 12:15 ` Andreas Schwab
2015-08-21 12:50 ` Óscar Fuentes
2015-08-21 13:44   ` Artur Malabarba
2015-08-21 13:31 ` Stefan Monnier
2015-08-21 14:21   ` Artur Malabarba [this message]
2015-08-21 15:16     ` Óscar Fuentes

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='CAAdUY-JONUVY=GHWhVtJpGqZPTVWusXw-rMNcs8RAjhiZg9m-A@mail.gmail.com' \
    --to=bruce.connor.am@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).