From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-29 b18754bb179: Minor improvements in c-ts-mode and docs
Date: Wed, 15 Feb 2023 21:39:21 +0200 [thread overview]
Message-ID: <83fsb6afbq.fsf@gnu.org> (raw)
In-Reply-To: <c6504014-71d8-9194-d317-f612f9f4e61c@yandex.ru> (message from Dmitry Gutov on Wed, 15 Feb 2023 20:53:37 +0200)
> Date: Wed, 15 Feb 2023 20:53:37 +0200
> Cc: emacs-devel@gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
>
> On 15/02/2023 20:35, Eli Zaretskii wrote:
> >> Date: Wed, 15 Feb 2023 20:14:29 +0200
> >> From: Dmitry Gutov <dgutov@yandex.ru>
> >>
> >> On 15/02/2023 20:02, Eli Zaretskii wrote:
> >>> + "C-c C-c" #'comment-region)
> >>
> >> Should we maybe take this opportunity to introduce c-ts-mode's users to
> >> the common bindings we use in other modes?
> >
> > What does this mean in practice?
>
> It would mean not adding the comment-region binding. Then I imagine
> people who transition to c-ts-mode, or start using it for the first
> time, might spend a little time looking for comment-related bindings,
> but in the end will learn to reach for it.
That'd be a hard sell for users of C mode, as I presume they are used
to have it. I do.
next prev parent reply other threads:[~2023-02-15 19:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <167648414913.7595.16030168421819097011@vcs2.savannah.gnu.org>
[not found] ` <20230215180229.75FF5C00613@vcs2.savannah.gnu.org>
2023-02-15 18:14 ` emacs-29 b18754bb179: Minor improvements in c-ts-mode and docs Dmitry Gutov
2023-02-15 18:31 ` Alan Mackenzie
2023-02-15 18:50 ` Dmitry Gutov
2023-02-15 19:37 ` Eli Zaretskii
2023-02-15 20:25 ` Dmitry Gutov
2023-02-16 7:09 ` Eli Zaretskii
2023-02-16 11:15 ` Dmitry Gutov
2023-02-16 12:01 ` Eli Zaretskii
2023-02-15 19:44 ` Alan Mackenzie
2023-02-15 20:29 ` Dmitry Gutov
2023-02-16 7:11 ` Eli Zaretskii
2023-02-15 18:35 ` Eli Zaretskii
2023-02-15 18:53 ` Dmitry Gutov
2023-02-15 19:39 ` Eli Zaretskii [this message]
2023-02-15 20:32 ` Dmitry Gutov
2023-02-16 7:32 ` Eli Zaretskii
2023-02-16 11:17 ` Dmitry Gutov
2023-02-16 12:03 ` Eli Zaretskii
2023-02-16 12:51 ` Dmitry Gutov
2023-02-16 15:19 ` Eli Zaretskii
2023-02-16 15:38 ` Dmitry Gutov
2023-02-16 15:53 ` Theodor Thornhill
2023-02-16 15:58 ` Eli Zaretskii
2023-02-16 20:09 ` Dmitry Gutov
2023-02-16 20:22 ` Eli Zaretskii
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=83fsb6afbq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@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 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).