emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: "François Pinard" <pinard@iro.umontreal.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: Changing [X] by something else
Date: Thu, 09 Feb 2012 17:26:07 +0100	[thread overview]
Message-ID: <87sjikt1ls.fsf@gmail.com> (raw)
In-Reply-To: <878vkdfemv.fsf@iro.umontreal.ca> ("François Pinard"'s message of "Wed, 08 Feb 2012 12:04:23 -0500")

Hello,

pinard@iro.umontreal.ca (François Pinard) writes:

> I notice in org.el that [X] is hard-wired, while I would have liked the
> possibility of changing it by [✓] 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,

-- 
Nicolas Goaziou

  parent reply	other threads:[~2012-02-09 16:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08 17:04 Changing [X] by something else François Pinard
2012-02-08 17:16 ` suvayu ali
2012-02-08 17:29   ` François Pinard
2012-02-08 17:40     ` suvayu ali
2012-02-09 16:26 ` Nicolas Goaziou [this message]
2012-02-09 16:54   ` François Pinard
2012-02-10 13:24     ` Allen S. Rout
2012-02-12  4:06       ` François Pinard
2012-02-10 13:23   ` Allen S. Rout
2012-02-11  9:40 ` Reiner Steib
2012-02-11 15:39 ` Jambunathan K
2012-02-11 19:10   ` Jambunathan K
2012-02-11 19:18     ` Jon Miller
2012-02-12  2:44   ` François Pinard
2012-02-12  6:19     ` Jambunathan K
2012-02-12 14:12       ` François Pinard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sjikt1ls.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=pinard@iro.umontreal.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).