From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: 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> 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]:53654) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fFwRP-0003Du-Tb for emacs-orgmode@gnu.org; Tue, 08 May 2018 02:49:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fFwRP-0007jO-0V for emacs-orgmode@gnu.org; Tue, 08 May 2018 02:49:39 -0400 In-Reply-To: <87sh7a9e33.fsf@gmail.com> (Aaron Ecay's message of "Wed, 02 May 2018 18:12:16 +0100") 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: Aaron Ecay Cc: emacs-orgmode@gnu.org, Rasmus Pank Roulund Hi Aaron, Aaron Ecay writes: > OK, that=CA=BCs good to know. I=CA=BCve held off on any pushing of the p= atch to > master until everything is worked out. In the meantime, I=CA=BCve put it= in > a branch =E2=80=9Corg-tempo=E2=80=9D. thanks for this. > I also added a second commit to that branch which implements my vision > of the upgrade path (deprecation warnings, etc.) For convenience, that > patch is also attached to this email. Thanks -- I tested it. 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. To be clear, the whole change still needs work for sure, and nothing is decided so far. But here is some food for thought on how to deprecate an Org feature more nicely. 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). But: what if we could use org-modules (or a similar mechanism) to tell the user: "Hey! We, the AlMighty Developers of Org think this feature is better not to be loaded by default for *every* user - but you, the independant rebel, might think otherwise, so here is your chance to turn it on by default in your configuration. Proceed (y/n)?" And voil=C3=A0! For example, the default value of org-modules could be an alist like: '((org-bbdb . t) (org-eww . t) (org-tempo . 'confirm) Then on first load, traverse this alist and prompt for confirmation for packages marked 'confirm. What do you think? --=20 Bastien