From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Changing [X] by something else Date: Thu, 09 Feb 2012 17:26:07 +0100 Message-ID: <87sjikt1ls.fsf@gmail.com> References: <878vkdfemv.fsf@iro.umontreal.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([140.186.70.92]:35343) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RvWrA-00058P-6l for emacs-orgmode@gnu.org; Thu, 09 Feb 2012 11:28:28 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RvWr4-0003wN-FV for emacs-orgmode@gnu.org; Thu, 09 Feb 2012 11:28:24 -0500 Received: from mail-ww0-f49.google.com ([74.125.82.49]:35804) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RvWr4-0003w8-AM for emacs-orgmode@gnu.org; Thu, 09 Feb 2012 11:28:18 -0500 Received: by wgbdt13 with SMTP id dt13so1400789wgb.30 for ; Thu, 09 Feb 2012 08:28:17 -0800 (PST) In-Reply-To: <878vkdfemv.fsf@iro.umontreal.ca> (=?utf-8?Q?=22Fran=C3=A7ois?= Pinard"'s message of "Wed, 08 Feb 2012 12:04:23 -0500") 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: =?utf-8?Q?Fran=C3=A7ois?= Pinard Cc: emacs-orgmode@gnu.org Hello, pinard@iro.umontreal.ca (Fran=C3=A7ois Pinard) writes: > I notice in org.el that [X] is hard-wired, while I would have liked the > possibility of changing it by [=E2=9C=93] in my things, which I find both= softer > and cleaner. Could these ([ ], [-] and [X]) be turned into variables? > The difficulty might be to recognize them properly, I guess. > > While it would be nice that I could change it, it might also have a > negative effect, making Org files less interoperable between people. On > the other hand, the TODO keywords are already changeable, so there is a > kind of precedent :-). Allowing to configure TODO keywords is mandatory if we aim at providing a decent tool for project planning. On the other hand, customizable check-boxes is only icing on the cake and doesn't add any functionality. Hence, I wouldn't call it a "kind of precedent". I don't think that we should allow basic structural elements to change. As you said, it will make Org documents less interoperable, but also less _recognizable_. What would happen to Org if every user could come up with its own syntax? Could we even talk about an "Org format" anymore? I'd rather keep it simple and consistent. It may be a bit ugly at times, but don't we all feel at home with plain text? Regards, --=20 Nicolas Goaziou