From: Eli Zaretskii <eliz@gnu.org>
To: john muhl <jm@pub.pink>
Cc: casouri@gmail.com, 65006@debbugs.gnu.org
Subject: bug#65006: 29.1.50; c-ts-mode: else block not indented right on TAB
Date: Tue, 08 Aug 2023 14:02:18 +0300 [thread overview]
Message-ID: <83bkfhokzp.fsf@gnu.org> (raw)
In-Reply-To: <87msz21woc.fsf@pub.pink> (message from john muhl on Mon, 07 Aug 2023 14:26:11 -0500)
> From: john muhl <jm@pub.pink>
> Cc: Yuan Fu <casouri@gmail.com>, 65006@debbugs.gnu.org
> Date: Mon, 07 Aug 2023 14:26:11 -0500
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Maybe we should track all those discussions, and voice our opinion
> > against changes whose reasons are not strong enough to justify
> > breakage? For example, this particular PR was around since Sep 2022,
> > so we should have had ample time to voice our objections.
> >
> > And anyway, this again raises the issue of Someone™ volunteering to
> > keep track of these developments. We already have 14 TS-based modes
> > in Emacs (on master), so this is not a trivial job, I think.
>
> I’m now subscribed to all of the relevant grammar repos and will try to
> keep up with changes there. I’m probably not the right person to voice
> an opinion on them without consulting higher authorities but hopefully
> that part won’t be required very often.
Thank you. Please post here whenever you see some changes planned
that might affect Emacs, and we will take it from there.
> > I agree that we have a problem here. The only question is how to
> > solve it in a reasonable way that will hold given our development and
> > release schedules, and given the schedules of users and distros
> > upgrading the Emacs versions.
>
> Do you think the benefit of having ts modes be core packages would be
> enough to justify whatever extra work that entails? It wouldn’t help
> with syncing up release schedules but “install the latest version from
> ELPA” might be enough better of an answer than “wait for the next Emacs
> release or build from master” for most people.
I think it's too early for us to make such conclusions. We need to
collect more data points and experience.
prev parent reply other threads:[~2023-08-08 11:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 2:43 bug#65006: 29.1.50; c-ts-mode: else block not indented right on TAB Mohammed Sadiq
2023-08-02 11:32 ` Eli Zaretskii
2023-08-02 16:03 ` john muhl via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-07 16:42 ` Yuan Fu
2023-08-07 18:29 ` john muhl via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-02 16:46 ` Yuan Fu
2023-08-02 17:05 ` Eli Zaretskii
2023-08-03 0:45 ` Yuan Fu
2023-08-03 6:37 ` Eli Zaretskii
2023-08-07 19:26 ` john muhl via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-08 11:02 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83bkfhokzp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65006@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=jm@pub.pink \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.