From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Robert Weiner Newsgroups: gmane.emacs.devel Subject: Re: Org Mode version to be bundled with Emacs 25? Date: Mon, 18 Jul 2016 12:40:10 -0400 Message-ID: References: <87eg6rm3vq.fsf@moondust.awandering> <83poqb0yxr.fsf@gnu.org> Reply-To: rswgnu@gmail.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a1140a15ae836c60537eba040 X-Trace: ger.gmane.org 1468860089 26300 80.91.229.3 (18 Jul 2016 16:41:29 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 18 Jul 2016 16:41:29 +0000 (UTC) To: "N. Jackson" , emacs-devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jul 18 18:41:27 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1bPBbj-000845-4v for ged-emacs-devel@m.gmane.org; Mon, 18 Jul 2016 18:41:27 +0200 Original-Received: from localhost ([::1]:48915 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bPBbi-0004Vq-EO for ged-emacs-devel@m.gmane.org; Mon, 18 Jul 2016 12:41:26 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33409) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bPBb5-0004Ve-Fl for emacs-devel@gnu.org; Mon, 18 Jul 2016 12:40:55 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bPBb1-0006do-3u for emacs-devel@gnu.org; Mon, 18 Jul 2016 12:40:46 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:55725) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bPBb0-0006dP-W1 for emacs-devel@gnu.org; Mon, 18 Jul 2016 12:40:43 -0400 Original-Received: from mail-oi0-f43.google.com ([209.85.218.43]:34664) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1bPBaz-0003rF-CI for emacs-devel@gnu.org; Mon, 18 Jul 2016 12:40:41 -0400 Original-Received: by mail-oi0-f43.google.com with SMTP id l65so174199233oib.1 for ; Mon, 18 Jul 2016 09:40:41 -0700 (PDT) X-Gm-Message-State: ALyK8tJxjuvEuyWBFapiRMfVX90Xt0Q4qaDgVnc1MdDS5KmP21yraNF2vhlO+XY89GZ7uUMYKaqvW9Mr0BhaKQ== X-Received: by 10.202.102.233 with SMTP id m102mr9019079oik.25.1468860039964; Mon, 18 Jul 2016 09:40:39 -0700 (PDT) Original-Received: by 10.202.199.143 with HTTP; Mon, 18 Jul 2016 09:40:10 -0700 (PDT) In-Reply-To: X-Gmail-Original-Message-ID: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:205813 Archived-At: --001a1140a15ae836c60537eba040 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, Jul 18, 2016 at 12:14 PM, John Wiegley wrote: > This is also a further argument for Org-mode to be released through ELPA, > rather than Emacs core, in which case none of this would be a real proble= m > -- > except for the recent bug reported concerning org-capture. =E2=80=8BThis makes sense as packages are likely to evolve much faster than= Emacs. But there is something missing in Emacs presently that would make this a much more attractive option to package developers who want the broadest base of users. There needs to be a simple, single function call to require a package which would automatically download, build, install and activate it (a flag could control whether or not this actually happened automatically or if the user were prompted to confirm, etc). Of course, there would be a way to require a particular version or the latest version of a package from the first matching archive in use by the package manager. There is already a flag to require that the package be digitally signed. Maybe this feature could be connected to autoloads as well. The main issue I see right now is that packages are installed on a per-user basis rather than a per-Emacs site basis, so you would get a lot more code instance duplication and version management issues than you would have with a package integrated into Emacs core. With this feature, Emacs core programmers could start referencing external packages as if they were already installed and Org could potentially move back out of core. If we can find consensus that this would be a good thing to add, I might be willing to develop it. Bob --001a1140a15ae836c60537eba040 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On M= on, Jul 18, 2016 at 12:14 PM, John Wiegley <jwiegley@gmail.com> wrote:
This is also a further argume= nt for Org-mode to be released through ELPA,
rather than Emacs core, in which case none of this would be a real problem = --
except for the recent bug reported concerning org-capture.

=E2=80=8BThis makes sense as packages are likely= to evolve much faster than Emacs.=C2=A0 But there is something missing in = Emacs presently that would make this a much more attractive option to packa= ge developers who want the broadest base of users.=C2=A0 There needs to be = a simple, single function call to require a package which would automatical= ly download, build, install and activate it (a flag could control whether o= r not this actually happened automatically or if the user were prompted to = confirm, etc).
Of course, there would be a way t= o require a particular version or the latest version of a package from the = first matching archive in use by the package manager.=C2=A0 There is alread= y a flag to require that the package be digitally signed.=C2=A0 Maybe this = feature could be connected to autoloads as well.

The main issue I see right now is that pac= kages are installed on a per-user basis rather than a per-Emacs site basis,= so you would get a lot more code instance duplication and version manageme= nt issues than you would have with a package integrated into Emacs core.

With this feature,= Emacs core programmers could start referencing external packages as if the= y were already installed and Org could potentially move back out of core.

If we can find co= nsensus that this would be a good thing to add, I might be willing to devel= op it.

Bob
=




--001a1140a15ae836c60537eba040--