From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aaron Ecay Subject: Re: Smooth transition for modules (was: [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. " References: <87lgd671k7.fsf@bzg.fr> <87o9i2p9qq.fsf@nicolasgoaziou.fr> <87k1sq6znz.fsf@bzg.fr> <871seyp6fr.fsf@nicolasgoaziou.fr> <874lju6tap.fsf@bzg.fr> <87bme1y7ft.fsf@gmail.com> <87h8nrbclk.fsf@gmail.com> <87lgd2whh9.fsf@gmx.us> <87sh7a9e33.fsf@gmail.com> <871semhcau.fsf_-_@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54639) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fFytK-0004Od-2Y for emacs-orgmode@gnu.org; Tue, 08 May 2018 05:26:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fFytJ-0007T2-4j for emacs-orgmode@gnu.org; Tue, 08 May 2018 05:26:38 -0400 In-Reply-To: <871semhcau.fsf_-_@gnu.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Bastien Cc: emacs-orgmode@gnu.org, Rasmus Pank Roulund Hi Bastien, 2018ko maiatzak 8an, Bastien-ek idatzi zuen: > Thanks -- I tested it.=20 Thanks :) > I like the idea of sending a warning to the user for > backward-incompatible changes but in this case, well, we take for > granted that org-tempo will be turned off by default in the next > release... but this is not decided yet. Indeed, the patch was written under that assumption. If the situation changes, (at least) some tweaks would be needed. >=20 > To be clear, the whole change still needs work for sure, and nothing > is decided so far. >=20 > But here is some food for thought on how to deprecate an Org feature > more nicely. >=20 > We have org-modules, which is an internal mechanism to load default > Org modules. Yes, this predates Emacs package system, and yes, we > should question the usefulness of it now (I do). >=20 > But: what if [...] I like this idea, but I also think that emacs=CA=BC packages feature is a better/newer way to implement something like this. What if: 1. We don=CA=BCt include org-tempo in org releases 2. We teach GNU ELPA to include org-tempo as a package (corresponding to stable org releases) 3. We teach to also do so (corresponding to nightly org releases) 4. We implement your suggested user prompt, but it will ask them if they want to install the org-tempo package from ELPA In this way, users who either install org from GNU ELPA or use the version bundled with emacs will get the latest release version of org-tempo from GNU ELPA. Those who install the nightly version of org will get the corresponding nightly version of org-tempo.* WDYT? (An alternative to step 3 above is to cater for the nightly release users by putting org-tempo in org-contrib. Then we wouldn=CA=BCt have to publish org-tempo on Org ELPA, only GNU ELPA. But this (a) doesn=CA=BCt he= lp those who install nightly org as opposed to nightly org-plus-contrib, and (b) means that org-tempo, unlike other packages in contrib, would have to be kept copyright-clean...so I=CA=BCm not sure it is a good choice.) Aaron * Those of us who install org from git might have to do something else to make sure the right version of org-tempo is loaded, but we=CA=BCre used = to living on the edge. :P --=20 Aaron Ecay