[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Moving Gnus development to Emacs?

From: CHENG Gao
Subject: Re: Moving Gnus development to Emacs?
Date: Thu, 31 Dec 2015 22:52:28 +0800
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (darwin)

*On Thu, 31 Dec 2015 22:35:24 +0800
* Also sprach Xue Fuqiao <address@hidden>:

> On Thu, Dec 31, 2015 at 8:29 PM, CHENG Gao <address@hidden> wrote:
>> John talked about new trend to move more codes into ELPA. Maybe it's
>> THE RIGHT WAY, to make emacs as emacs-core (with only bare
>> functions) and all others packges (core as ELPA, third party as
>> Melpa etc, or even PPA).
> FYI - there were some discussions about this proposal earlier this
> year:
> * https://lists.gnu.org/archive/html/emacs-devel/2015-11/msg00212.html
> * https://lists.gnu.org/archive/html/emacs-devel/2015-11/msg00146.html
> IIRC Atom is using this kind of architecture. It has a really basic
> core, and most of its features are available as packages, including
> some very "basic" features, like settings-view (similar to `M-x
> customize' in Emacs), find-and-replace, status-bar (similar to mode
> line in Emacs), tabs (GUI tabs, not the tab character), language
> modes, etc.
> But this approach also has its downside. See the links above for some
> related discussions.

Thanks for the info. Yes I know Atom does this, and also VS Code recently.

>> If package.el becomes APT like, that'll be cool, really cool.
> What does this mean? Command-line tools like `apt', `apt-get' or
> `apt-cache' (or `apm' in Atom)? If so, I think a simple wrapper script
> to `emacs --batch' is enough.

I don't mean this. Sorry for my ambiguous expression.
Mainly I mean package.el can do dependency check and install proper
dependent packages. Also can handle different Emacs versions since
packages may stop supporting some Emacs versions or not yet catch up with
latest version. But it may be too complicated.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]