From: Yuri Khan <yuri.v.khan@gmail.com>
To: PEDRO ANDRES ARANDA GUTIERREZ <paranda@it.uc3m.es>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Just a thought about comment-line
Date: Sun, 31 May 2020 16:57:37 +0700 [thread overview]
Message-ID: <CAP_d_8WqXE7N3zB=PNpMCgGGEHB_1L_ho+38inDcRdi25-FNvQ@mail.gmail.com> (raw)
In-Reply-To: <CAPoMwp3rxz+oBGM=aHnPPqT_cvDzT7-b+sMK9-PbRMKVt7zjJg@mail.gmail.com>
On Sun, 31 May 2020 at 14:40, PEDRO ANDRES ARANDA GUTIERREZ <paranda@it.uc3m.es>
> Take any file, code or not, but let's say it is code...
> Now select two or more lines. The mark should be at the beginning of a line
> and the point at the beginning of a line two or more lines further down. If you copy this region and paste it somewhere else you get what you want.
>
> However let's suppose that your theme is highlighting the region and you comment the region with M-x comment-line. You will have the line at the point:
> 1.- not highlighted before M-x comment-line
> 2.- commented after M-x comment-line
Since you are selecting whole lines to be commented, you might find
comment-dwim (M-;) more to your liking. (If you select partial lines,
it may also split them if the current mode only has end-of-line
comments.)
FWIW I agree with you: a region that ends at the physical start of
line, before indentation, should not be considered to include that
line.
next prev parent reply other threads:[~2020-05-31 9:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-31 7:39 Just a thought about comment-line PEDRO ANDRES ARANDA GUTIERREZ
2020-05-31 9:57 ` Yuri Khan [this message]
2020-05-31 16:58 ` Drew Adams
2020-05-31 17:15 ` Stefan Monnier
2020-05-31 18:05 ` Drew Adams
2020-05-31 19:05 ` Stefan Monnier
2020-05-31 21:53 ` Drew Adams
2020-05-31 17:42 ` Dmitry Gutov
2020-05-31 18:08 ` Drew Adams
2020-05-31 18:31 ` Dmitry Gutov
2020-05-31 21:54 ` Drew Adams
2020-06-01 5:18 ` PEDRO ANDRES ARANDA GUTIERREZ
2020-06-01 5:29 ` PEDRO ANDRES ARANDA GUTIERREZ
2020-05-31 14:40 ` Eli Zaretskii
2020-05-31 16:53 ` Drew Adams
2020-06-01 6:14 ` Clément Pit-Claudel
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='CAP_d_8WqXE7N3zB=PNpMCgGGEHB_1L_ho+38inDcRdi25-FNvQ@mail.gmail.com' \
--to=yuri.v.khan@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=paranda@it.uc3m.es \
/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).