From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. " References: <87wowoh1m9.fsf@aquinas.i-did-not-set--mail-host-address--so-tickle-me> <871sevime2.fsf@nicolasgoaziou.fr> <87h8nm7zhy.fsf@gmx.us> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58065) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fFokz-0000Ph-F0 for emacs-orgmode@gnu.org; Mon, 07 May 2018 18:37:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fFokw-0003O1-7f for emacs-orgmode@gnu.org; Mon, 07 May 2018 18:37:21 -0400 Received: from [195.159.176.226] (port=41201 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fFokw-0003NR-0b for emacs-orgmode@gnu.org; Mon, 07 May 2018 18:37:18 -0400 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1fFoim-0001d9-Ja for emacs-orgmode@gnu.org; Tue, 08 May 2018 00:35:04 +0200 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: emacs-orgmode@gnu.org Carsten Dominik writes: > On Sat, May 5, 2018 at 8:02 PM Rasmus wrote: > >> Nicolas Goaziou writes: >> >> > Hello, >> > >> > Steve Downey writes: >> > >> >> Asking users to accept any breakage in the tool they use to get work >> done >> >> is a lot. Changes in UI in emacs are opt-in. >> >> >> >> Even if the change is the right thing to do. >> > >> > I think some of you (basically, anyone thinking we should enable "> > TAB" by default ;)) are missing the point. >> > >> > >> > The first important thing to understand is that, even if we enable >> > `org-tempo' by default, next Org release /will break/ for some of us. >> > >> > - It will break because `org-tempo' is only 99% backward-compatible. So >> > anyone having customizing templates is bound to change them. >> > >> > - It will break because there are 9 other incompatible changes between >> > 9.1 and 9.2. >> > >> > So, asking to load `org-tempo' by default just to avoid breaking users >> > set-up is a wrong argument. It will only "protect" those among us that >> > use "> > incompatible changes. IOW, updating Org from 9.1 to 9.2 will not be >> > smooth for everyone. No matter what `org-tempo' becomes. >> >> Nicolas, I have been wondering about something, reading all these posts, >> irrespective of whether tempo is loaded by default or not (I don’t care). >> >> Do you think org-tempo should try to detect "old" versions of >> org-structure-template-alist and give a better error if it sees one? I >> don’t know what the "best practice" is this case... >> > > Yes, it absolutely should. Thanks. I guess it would be enough to check if the elements of the alist are cons (newer Orgs) or lists (older orgs). A more "complex" procedure could look for at the content of the ca?dr, I guess, but I don’t know if that’s necessary. Rasmus -- I feel emotional landscapes they puzzle me