Gnus development mailing list
 help / color / mirror / Atom feed
From: Xue Fuqiao <xfq.free@gmail.com>
To: CHENG Gao <chenggao@royau.me>
Cc: ding@gnus.org, Emacs-devel <emacs-devel@gnu.org>
Subject: Re: Moving Gnus development to Emacs?
Date: Thu, 31 Dec 2015 22:35:24 +0800	[thread overview]
Message-ID: <CAAF+z6FXiz3ysP=v+UQaJfEXmh4J+qKibRvqJmkS-WUUZCtHHA@mail.gmail.com> (raw)
In-Reply-To: <m2k2nun6mi.fsf@royau.me>

On Thu, Dec 31, 2015 at 8:29 PM, CHENG Gao <chenggao@royau.me> 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.

> 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.



  reply	other threads:[~2015-12-31 14:35 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-30 11:43 Lars Magne Ingebrigtsen
     [not found] ` <mailman.1827.1451475821.29210.sxemacs-devel-sxemacs.org@lists.sxemacs.org>
2015-12-30 14:33   ` Moving Gnus development to Emacs Steve Youngs
2015-12-30 15:15     ` Ivan Shmakov
2016-01-01 19:21     ` Steinar Bang
2016-01-02  3:28     ` Lars Magne Ingebrigtsen
2015-12-30 16:33 ` Moving Gnus development to Emacs? raman
2015-12-30 19:05   ` Jay Belanger
2015-12-30 19:25     ` Nikolaus Rath
2015-12-31 17:40     ` Lars Magne Ingebrigtsen
2015-12-31 18:35       ` Benjamin Slade
2015-12-30 18:44 ` John Wiegley
2015-12-31  0:46 ` Katsumi Yamaoka
2015-12-31 13:50   ` Eli Zaretskii
2015-12-31  9:18 ` Julien Danjou
2015-12-31  9:40 ` David Engster
2015-12-31 11:43   ` Michael Albinus
2015-12-31 12:29     ` CHENG Gao
2015-12-31 14:35       ` Xue Fuqiao [this message]
2015-12-31 14:52         ` CHENG Gao
2016-01-01  0:10           ` Xue Fuqiao
2016-01-01  7:02             ` CHENG Gao
2015-12-31 17:10   ` Lars Magne Ingebrigtsen
2015-12-31 17:15     ` Adam Sjøgren
2016-01-02 17:39   ` Lars Magne Ingebrigtsen
2016-01-02 20:31     ` Steinar Bang
2016-01-03 18:24     ` Bill Wohler
2016-01-04  0:48       ` Lars Magne Ingebrigtsen
2016-01-04  1:05         ` John Wiegley
2016-01-04  3:47     ` Steve Youngs
2016-01-06  7:18       ` Lars Magne Ingebrigtsen
2016-01-06  7:38         ` CHENG Gao
2016-01-06  8:50         ` Andreas Schwab
2016-01-25 15:07     ` Ted Zlatanov
2016-01-28 12:45     ` Greg Troxel
2015-12-31 10:15 ` Eric Abrahamsen
2015-12-31 17:43   ` Lars Magne Ingebrigtsen
2016-01-01 21:43   ` Göktuğ Kayaalp
2015-12-31 17:04 ` Uwe Brauer
2016-01-18  7:26 gnus-summary-refer-parent-article bug Dave Abrahams
2016-01-18 12:43 ` Alan Schmitt
2016-01-18 15:47   ` Dave Abrahams
2016-01-19  0:25     ` Katsumi Yamaoka
2016-01-19 15:59       ` Dave Abrahams
2016-01-19 22:10         ` Katsumi Yamaoka
2016-01-20 11:04           ` Alan Schmitt
2016-01-20 23:04             ` Katsumi Yamaoka
2016-01-21 10:21               ` Alan Schmitt
2016-01-22  2:37                 ` Moving Gnus development to Emacs? Katsumi Yamaoka
2016-01-22  7:53                   ` Alan Schmitt
2016-01-22  9:45                     ` Katsumi Yamaoka
2016-01-22 11:28                       ` Michael Albinus
2016-01-24 23:35                         ` Katsumi Yamaoka
2016-01-25  1:58                           ` Mike Kupfer
2016-01-25  3:11                             ` Katsumi Yamaoka
2016-01-25 13:12                             ` Alan Schmitt
2016-01-22 12:25                       ` Alan Schmitt
2016-01-25  1:37                   ` Katsumi Yamaoka
2016-02-06  5:51                   ` Lars Ingebrigtsen
2016-02-06 14:36                     ` Adam Sjøgren
2016-02-06 14:38                       ` Adam Sjøgren

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='CAAF+z6FXiz3ysP=v+UQaJfEXmh4J+qKibRvqJmkS-WUUZCtHHA@mail.gmail.com' \
    --to=xfq.free@gmail.com \
    --cc=chenggao@royau.me \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    /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.
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 NNTP newsgroup(s).