unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: theo@thornhill.no, emacs-devel@gnu.org
Subject: Re: emacs-29 b18754bb179: Minor improvements in c-ts-mode and docs
Date: Thu, 16 Feb 2023 22:22:23 +0200	[thread overview]
Message-ID: <838rgx2we8.fsf@gnu.org> (raw)
In-Reply-To: <619d319b-1339-4f2a-9b55-5d8629c1227b@yandex.ru> (message from Dmitry Gutov on Thu, 16 Feb 2023 22:09:21 +0200)

> Date: Thu, 16 Feb 2023 22:09:21 +0200
> Cc: emacs-devel@gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> 
> > I don't see a reason to add C-specific features to c-ts-mode as long
> > as the general ones do a decent job.  After reviewing the features and
> > their current equivalents in c-ts-mode, I asked for only one to be
> > added: electric-pound.  All the rest I think are in relatively good
> > shape as we are.  So are you sure we are at a crossroads and not
> > already home free?
> 
> I don't know. The commit which gave rise to this thread surprised me 
> already.

I already explained the rationale for that.

> All right. So it seems like c-indent-line-or-region can be replaced with 
> indent-for-tab-command without any particular loss?

That's what c-ts-mode does.



      reply	other threads:[~2023-02-16 20:22 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
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 [this message]

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=838rgx2we8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=theo@thornhill.no \
    /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).