unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: theo@thornhill.no, casouri@gmail.com, spacibba@aol.com,
	emacs-devel@gnu.org
Subject: Re: c-ts-mode
Date: Fri, 08 Sep 2023 18:34:39 +0300	[thread overview]
Message-ID: <83jzt0wueo.fsf@gnu.org> (raw)
In-Reply-To: <CALDnm515n1rUDJVMYrRoMV3dbRbu5t1SJuTgnEJM4L6CGQktag@mail.gmail.com> (message from João Távora on Fri, 8 Sep 2023 16:15:09 +0100)

> From: João Távora <joaotavora@gmail.com>
> Date: Fri, 8 Sep 2023 16:15:09 +0100
> Cc: theo@thornhill.no, casouri@gmail.com, spacibba@aol.com, 
> 	emacs-devel@gnu.org
> 
> > > I guess this means we should add a TODO item for supporting such
> > > external specifications?
> >
> > Done; patches welcome.
> 
> I couldn't find your TODO item (in etc/TODO at least).

Chrystal ball says you looked on master.  I made my change on the
emacs-29 branch instead.

> But I'm curious as to how you will phrase it: "supporting" can have
> many meanings.
> 
> If it means "have some kind of interface for using" then Emacs already
> has one, which is `eglot-format`.  Although indirect (because LSP), it
> is a pretty effective in abstracting away different specs of different
> such tools (clang-format, prettier, eslint, etc).

I think we should try to support this without LSP servers.

> But if "supporting" means "plug into indent-line-function and
> indent-region-function", then it's going to be relatively hard, because
> as I explained, these are formatters, not indenters, so it's a bit
> of a round-peg, square-hole problem.

Which, as we all know, is a problem that was solved at least once.

> So if you want to keep the existing interface of those two functions
> (which would be ideal, since a lot of tooling already depends on
> them), there would have to be some way to communicate with these
> tools so that they only talk about indentation.  Not saying it's
> impossible, but it's hard, at least when LSP is used for abstracting
> away differences.

Let's talk after you read what I wrote in TODO.



  reply	other threads:[~2023-09-08 15:34 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <r6t7xfcchagyl72ltdrcavncbpvba7badcoh4yimleoynmzfvb.ref@elkspm3vozuv>
2023-08-30 23:52 ` c-ts-mode Ergus
2023-09-01  4:14   ` c-ts-mode Yuan Fu
2023-09-07  9:25     ` c-ts-mode João Távora
2023-09-07  9:37       ` c-ts-mode Eli Zaretskii
2023-09-07 15:58         ` c-ts-mode João Távora
2023-09-07 17:10           ` c-ts-mode Eli Zaretskii
2023-09-07 17:53             ` c-ts-mode João Távora
2023-09-07 18:13               ` c-ts-mode Eli Zaretskii
2023-09-07 18:23                 ` c-ts-mode João Távora
2023-09-07 18:32                   ` c-ts-mode Eli Zaretskii
2023-09-07 22:01                     ` c-ts-mode João Távora
2023-09-08  6:14                       ` c-ts-mode Eli Zaretskii
2023-09-08  7:25                         ` c-ts-mode João Távora
2023-09-08 11:25                           ` c-ts-mode Eli Zaretskii
2023-09-08 12:38                             ` c-ts-mode João Távora
2023-09-08 13:11                               ` c-ts-mode Eli Zaretskii
2023-09-08 13:32                                 ` c-ts-mode Eli Zaretskii
2023-09-08 15:15                                   ` c-ts-mode João Távora
2023-09-08 15:34                                     ` Eli Zaretskii [this message]
2023-09-08 15:56                                       ` c-ts-mode João Távora
2023-09-08 18:23                                         ` c-ts-mode Eli Zaretskii
2023-09-08 18:30                                           ` c-ts-mode João Távora
2023-09-08 18:54                                             ` c-ts-mode Eli Zaretskii
2023-09-08 19:42                                               ` c-ts-mode João Távora
2023-09-09  6:09                                                 ` c-ts-mode Eli Zaretskii
2023-09-08 19:58                               ` c-ts-mode Petteri Hintsanen
2023-09-08 20:27                                 ` c-ts-mode João Távora
2023-09-09  6:19                                 ` c-ts-mode Eli Zaretskii
2023-09-13 16:15                                   ` c-ts-mode Petteri Hintsanen
2023-09-12  0:34                             ` c-ts-mode Yuan Fu
2023-09-12  7:45                               ` c-ts-mode João Távora
2023-09-12  8:00                                 ` c-ts-mode Po Lu
2023-09-12  9:51                                   ` c-ts-mode João Távora

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=83jzt0wueo.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=casouri@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=spacibba@aol.com \
    --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).