From: Dmitry Gutov <dgutov@yandex.ru>
To: Drew Adams <drew.adams@oracle.com>,
Yuri Khan <yuri.v.khan@gmail.com>,
PEDRO ANDRES ARANDA GUTIERREZ <paranda@it.uc3m.es>
Cc: emacs-devel@gnu.org
Subject: Re: Just a thought about comment-line
Date: Sun, 31 May 2020 21:31:07 +0300 [thread overview]
Message-ID: <cf01c196-74e5-d5e8-6058-72895db6407f@yandex.ru> (raw)
In-Reply-To: <47fc942f-62e1-4efc-9d67-db292177044e@default>
On 31.05.2020 21:08, Drew Adams wrote:
> You're fairly sure for whom? For you? Not for me.
The only complaints against comment-dwim I have seen were along the
lines "I want to micromanage how comments are made", and not "this
code-writing scenario becomes suboptimal".
Are you still writing code? I'm surprised, not having seen any patches
from you in a long while.
> Tell me why Common Lisp behavior for block comments
> (#|...|#) is missing? I don't mean that those macro
> chars are missing, but that the block-commenting
> behavior (nesting, unnesting) is missing.
You might want to elaborate.
It definitely can create nested comments (i.e. in the cases they are
really needed, when you call it on a region containing both commented
and non-commented lines).
next prev parent reply other threads:[~2020-05-31 18:31 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
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 [this message]
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=cf01c196-74e5-d5e8-6058-72895db6407f@yandex.ru \
--to=dgutov@yandex.ru \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=paranda@it.uc3m.es \
--cc=yuri.v.khan@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 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).