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: <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> <87wowi8100.fsf@gmx.us> <87wowgr1rp.fsf@gmail.com> <87a7tb6pt3.fsf@gmx.us> <87y3gvrmku.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]:47659) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fKljf-0005fn-7L for emacs-orgmode@gnu.org; Mon, 21 May 2018 10:24:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fKljc-00022D-2X for emacs-orgmode@gnu.org; Mon, 21 May 2018 10:24:27 -0400 Received: from mout.gmx.net ([212.227.15.19]:56021) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fKljb-00021e-PR for emacs-orgmode@gnu.org; Mon, 21 May 2018 10:24:24 -0400 Received: from W530 ([109.91.34.4]) by mail.gmx.com (mrgmx002 [212.227.17.184]) with ESMTPSA (Nemesis) id 0M92lh-1fXBPP0o9t-00COPy for ; Mon, 21 May 2018 16:24:22 +0200 In-Reply-To: <87y3gvrmku.fsf@gmail.com> (Aaron Ecay's message of "Tue, 08 May 2018 01:57:21 +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: emacs-orgmode@gnu.org Hi, Aaron Ecay writes: > Hi Rasmus, > > 2018ko maiatzak 7an, Rasmus-ek idatzi zuen: > >>=20 >> They=E2=80=99d already have the "old" behavior if it=E2=80=99s enabled b= y default in >> org.el.=20=20 > > Indeed, my suggestion is not an alternative to keeping (what is now > called) org-tempo turned on by default indefinitely. It is an > alternative to turning org-tempo off suddenly. > >> Perhaps I=E2=80=99m too cruel or harsh after many years of dealing with = the >> Emacs-way, but I do think that such as change is adequatly documented >> in ORG-NEWS and the manual. (Days after a new release there will also >> be a stackoverflow question for the Googlers).=20=20 > > Here I am much more conservative than you: I think that puzzling users > so that they ask questions on stack overflow is an outcome that should > be avoided if possible. I also think experience shows that ORG-NEWS is > missed by a significant fraction of users. That is a nice thought, at least in theory. I guess my worry is about the "costs" of implementing such practices. Perhaps we could ask people if they want to have the ORG-NEWS file displayed when a new version of Org is installed. :) > Besides, I am a programmer not a writer so I believe in the power of > code over prose :P I am not a programmer, so perhaps therein lies the difference. >> Customize-changed would bring up the changes to >> org-structure-template-alist, which mentions Org Tempo. > > Interesting. I didn=CA=BCt know about that function. I just tried M-x > customize-changed RET Org 9.0 RET. That gives an error; it seems to > only work based on emacs versions and not package versions. That=CA=BCs > unfortunate, it would have been nice if people who install org from ELPA > could use the function to keep up with org changes independently from > their emacs version. (In fact, I just sent this as a feature request to > the emacs bug tracker, #31383) I did not know that. Thanks. Rasmus --=20 Dobbelt-A