Re: Adding AUCTeX to core Re: Why not include all ELPA packages in an Emacs release?

[Philip Kaludercic <philipk@posteo.net>]

Jeremy Bryant <jb@jeremybryant.net> writes:

> Andrea Corallo <acorallo@gnu.org> writes:
>
>> Philip Kaludercic <philipk@posteo.net> writes:
>>
>>> Arash Esbati <arash@gnu.org> writes:
>>>
>>>> Eli Zaretskii <eliz@gnu.org> writes:
>>>>
>>>>> If there are packages on ELPA which we consider to be a must for users
>>>>> (I don't think there are, but maybe I'm forgetting something), lets
>>>>> add them to core instead.
>>>>
>>>> If Emacs considers in-buffer completion an important feature, then I'd
>>>> say corfu and cape are must.  
>>>
>>> I am not familiar with cape, but IIRC the issue with corfu is that
>>> without any further changes, it doesn't support non-graphical Emacs,
>>> right?
>>>
>>>>                               vertico and marginalia are also must in my
>>>> book since they offer a better experience with vertical minibuffer
>>>> completion.
>>>
>>> "Better", in this case, than `fido-vertical-mode'?
>>>
>>>> And while we're at it: There are sometimes requests for adding AUCTeX to
>>>> core.  Do you have an opinion about that?
>>>
>>> I would certainly be a fan of that move.
>>
>> I support AUCTeX inclusion as well.
>>
>>   Andrea
>
> I can volunteer for some of this work under the guidance of the
> Emacs maintainers and the AUCTeX maintainers (as I have contributed some
> patches already.).  AUCTeX follows the Emacs development guidelines so
> it should be easier.
>
> As mentioned by Eli, AUCTeX could be merged in core but not enabled by
> default to start.
>
> What would be the most important next step required?

Wait, is the plan to add AUCTeX directly to emacs.git, or to include
AUCTeX in the packages that would be bundled with the release-tarball?

-- 
	Philip Kaludercic on peregrine