[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Unifying "foo-mode"s and "foo-ts-mode"s
From: |
Philip Kaludercic |
Subject: |
Re: Unifying "foo-mode"s and "foo-ts-mode"s |
Date: |
Fri, 30 Dec 2022 15:57:59 +0000 |
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Philip Kaludercic <philipk@posteo.net>
>> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org, Yuan Fu
>> <casouri@gmail.com>
>> Date: Fri, 30 Dec 2022 15:02:37 +0000
>>
>> Yes, I do understand this point, yet my impression has been that this
>> was not always necessary. The relative complexity of cc-mode might
>> necessitate a separate mode, but I don't see why that should be the rule
>> instead of an exception?
>
> CC Mode means C, C++, and Java already. If these 3 are separate
> modes, how to make your proposal work for them and for the others as
> well, in a way that is (1) convenient and easily understood by users,
> and (2) simple and safe enough to implement so that we don't
> inadvertently screw existing modes?
In some other response I have said that cc-mode seems too complicated
for now. I agree that it is a better approach to take some time and
develop the right infrastructure going forward towards Emacs 30. But
would this mean that the "...-ts-mode"s are to be regarded as
experimental demonstrations?
- Re: Need for "-ts-mode" modes, (continued)
- Re: Need for "-ts-mode" modes, Eli Zaretskii, 2022/12/29
- Re: Need for "-ts-mode" modes, Eli Zaretskii, 2022/12/29
- Unifying "foo-mode"s and "foo-ts-mode"s, Philip Kaludercic, 2022/12/30
- Re: Unifying "foo-mode"s and "foo-ts-mode"s, Theodor Thornhill, 2022/12/30
- Re: Unifying "foo-mode"s and "foo-ts-mode"s, Philip Kaludercic, 2022/12/30
- Re: Unifying "foo-mode"s and "foo-ts-mode"s, Theodor Thornhill, 2022/12/30
- Re: Unifying "foo-mode"s and "foo-ts-mode"s, Philip Kaludercic, 2022/12/30
- Re: Unifying "foo-mode"s and "foo-ts-mode"s, Theodor Thornhill, 2022/12/30
- Re: Unifying "foo-mode"s and "foo-ts-mode"s, Philip Kaludercic, 2022/12/30
- Re: Unifying "foo-mode"s and "foo-ts-mode"s, Eli Zaretskii, 2022/12/30
- Re: Unifying "foo-mode"s and "foo-ts-mode"s,
Philip Kaludercic <=
- Re: Unifying "foo-mode"s and "foo-ts-mode"s, Eli Zaretskii, 2022/12/30
- Re: Unifying "foo-mode"s and "foo-ts-mode"s, Philip Kaludercic, 2022/12/30
- Re: Unifying "foo-mode"s and "foo-ts-mode"s, Eli Zaretskii, 2022/12/30
- Re: Unifying "foo-mode"s and "foo-ts-mode"s, Philip Kaludercic, 2022/12/30
- Re: Unifying "foo-mode"s and "foo-ts-mode"s, Eli Zaretskii, 2022/12/31
- Re: Unifying "foo-mode"s and "foo-ts-mode"s, Eli Zaretskii, 2022/12/30
- Re: Unifying "foo-mode"s and "foo-ts-mode"s, Philip Kaludercic, 2022/12/30
- Re: Unifying "foo-mode"s and "foo-ts-mode"s, Eli Zaretskii, 2022/12/30
- Re: Unifying "foo-mode"s and "foo-ts-mode"s, Philip Kaludercic, 2022/12/30
- Re: Unifying "foo-mode"s and "foo-ts-mode"s, Stefan Monnier, 2022/12/30