From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [RFC] Change some defcustoms into defcont Date: Wed, 23 Oct 2013 10:56:17 +0200 Message-ID: <87vc0otlfy.fsf@gmail.com> References: <871u3g5nwx.fsf@gmail.com> <87mwm33sv1.fsf@gmail.com> <87a9i2522c.fsf@gmail.com> <7839A647-8D17-47A9-A65D-5FD7110ED082@gmail.com> <874n8avenk.fsf@gmail.com> <87zjq1tyxy.fsf@gmail.com> <9ED40360-BFB2-4F8C-BADB-6F0A798C9742@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46503) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VYuEc-0006L8-FN for emacs-orgmode@gnu.org; Wed, 23 Oct 2013 04:56:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VYuEU-0007Mc-0f for emacs-orgmode@gnu.org; Wed, 23 Oct 2013 04:56:10 -0400 Received: from mail-wg0-x233.google.com ([2a00:1450:400c:c00::233]:38963) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VYuET-0007MU-P9 for emacs-orgmode@gnu.org; Wed, 23 Oct 2013 04:56:01 -0400 Received: by mail-wg0-f51.google.com with SMTP id l18so456417wgh.6 for ; Wed, 23 Oct 2013 01:56:00 -0700 (PDT) In-Reply-To: <9ED40360-BFB2-4F8C-BADB-6F0A798C9742@gmail.com> (Carsten Dominik's message of "Tue, 22 Oct 2013 12:34:34 +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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Carsten Dominik Cc: Org Mode List Hello, Carsten Dominik writes: > can you remind me what the bug was? The taskjuggler issue? Correct. I will fix it today. > Yes, as I said, I do see all these problems, but I also feel the responsibility > to break as few as possible existing configurations. I understand. Though, almost any serious change breaks some existing configuration. It is unfortunate, but I hope it will not prevent us from correcting past, and future, mistakes. Without that right to be wrong, we'd better plan Org development a very long time ahead and cross fingers hoping we will never fail. Don't cross too hard. > If you want, I can take a shot at documenting this properly. I'm not convinced by that documentation thing, i.e. "we allow you to change the string, but we remind you that you shouldn't do it". It even goes against my initial suggestion, so I cannot say I "want" anything in that area. Unless, that is, you're talking about a deprecation warning, e.g. "In future releases, this variable will not be customizable anymore, so be careful when changing its default value". But, IIUC, that's not what you want. Regards, -- Nicolas Goaziou