From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: [RFC] Change some defcustoms into defcont Date: Sun, 20 Oct 2013 10:47:42 +0200 Message-ID: <871u3g5nwx.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40438) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VXoff-0004R2-QG for emacs-orgmode@gnu.org; Sun, 20 Oct 2013 04:47:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VXofX-0003Vg-D2 for emacs-orgmode@gnu.org; Sun, 20 Oct 2013 04:47:35 -0400 Received: from mail-wg0-x233.google.com ([2a00:1450:400c:c00::233]:64554) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VXofX-0003Vc-69 for emacs-orgmode@gnu.org; Sun, 20 Oct 2013 04:47:27 -0400 Received: by mail-wg0-f51.google.com with SMTP id l18so5365764wgh.30 for ; Sun, 20 Oct 2013 01:47:25 -0700 (PDT) Received: from selenimh ([91.224.148.150]) by mx.google.com with ESMTPSA id s4sm43868311wiy.1.2013.10.20.01.47.24 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 20 Oct 2013 01:47:24 -0700 (PDT) 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: Org Mode List Hello, I'd like to suggest changing the following defcustom variables into defconst: - org-deadline-string - org-scheduled-string - org-closed-string - org-clock-string - org-comment-string - org-quote-string - org-effort-property - org-archive-tag There's no fundamental reason to change these, as they belong to Org syntax, much like star character for headlines and ":END:" closing string for drawers. They can also introduce bugs in code when modified (e.g. modifying `org-effort-property' breaks `ox-taskjuggler'). Of course, this can be avoided with careful checks, but this puts an extra burden on developers for a tiny benefit for the user. Eventually, they can be costly, since changing any of them implies that cache in every Org buffer must be erased. Allowing customization is generally good, but I think Org syntax should never be a moving target. Note that this shouldn't introduce much backward incompatibility (unless user changes them through customize interface) since a defconst can still be setq'ed and variables will still be used in code base. Opinions? Regards, -- Nicolas Goaziou