From: Eli Zaretskii <eliz@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: theo@thornhill.no, emacs-devel@gnu.org, casouri@gmail.com
Subject: Re: Unifying "foo-mode"s and "foo-ts-mode"s
Date: Sat, 31 Dec 2022 08:38:32 +0200 [thread overview]
Message-ID: <83a6345b87.fsf@gnu.org> (raw)
In-Reply-To: <87cz8077n4.fsf@posteo.net> (message from Philip Kaludercic on Sat, 31 Dec 2022 00:13:03 +0000)
> From: Philip Kaludercic <philipk@posteo.net>
> Cc: theo@thornhill.no, emacs-devel@gnu.org, casouri@gmail.com
> Date: Sat, 31 Dec 2022 00:13:03 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> That answers my question. The point is whether the usage of ...-ts-mode
> >> major modes is recommended or provided with a "we reserve the right to
> >> change anything"-like caveat, so one shouldn't rely too much on their
> >> public interface.
> >
> > I guess it depends on who "one" is for this purpose. Which code wants
> > to rely on these symbols, and why?
>
> Both emacs-internal packages and external packages that depend on Emacs
> 29.
Are there any concrete examples of those? If not, let's delay this
discussion until such concrete cases emerge, because discussing a
theoretical issue is many times not very productive, as it's easy to
talk past each other when there's nothing concrete in sight.
next prev parent reply other threads:[~2022-12-31 6:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 17:08 Need for "-ts-mode" modes Philip Kaludercic
2022-12-29 17:42 ` Eli Zaretskii
2022-12-29 18:26 ` Philip Kaludercic
2022-12-29 19:27 ` Yuan Fu
2022-12-29 19:42 ` Eli Zaretskii
2022-12-30 4:05 ` Richard Stallman
2022-12-30 8:49 ` Eli Zaretskii
2022-12-29 19:57 ` Eli Zaretskii
2022-12-29 20:23 ` Eli Zaretskii
2022-12-30 10:58 ` Unifying "foo-mode"s and "foo-ts-mode"s Philip Kaludercic
2022-12-30 12:50 ` Theodor Thornhill
2022-12-30 13:08 ` Philip Kaludercic
2022-12-30 13:19 ` Theodor Thornhill
2022-12-30 15:02 ` Philip Kaludercic
2022-12-30 15:24 ` Theodor Thornhill
2022-12-30 15:45 ` Philip Kaludercic
2022-12-30 15:42 ` Eli Zaretskii
2022-12-30 15:57 ` Philip Kaludercic
2022-12-30 16:20 ` Eli Zaretskii
2022-12-30 16:39 ` Philip Kaludercic
2022-12-30 17:05 ` Eli Zaretskii
2022-12-31 0:13 ` Philip Kaludercic
2022-12-31 6:38 ` Eli Zaretskii [this message]
2022-12-30 15:02 ` Eli Zaretskii
2022-12-30 15:20 ` Philip Kaludercic
2022-12-30 15:52 ` Eli Zaretskii
2022-12-30 16:09 ` Philip Kaludercic
2022-12-30 16:30 ` Stefan Monnier
2022-12-30 17:03 ` Eli Zaretskii
2023-01-01 3:03 ` Richard Stallman
2023-01-01 7:28 ` Eli Zaretskii
2023-01-03 4:07 ` Richard Stallman
2023-01-03 12:11 ` Eli Zaretskii
2023-01-05 3:34 ` Richard Stallman
2022-12-30 17:10 ` Gregory Heytings
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=83a6345b87.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
--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).