From: "Allen S. Rout" <asr@ufl.edu>
To: emacs-orgmode@gnu.org
Subject: Re: Changing [X] by something else
Date: Fri, 10 Feb 2012 08:23:27 -0500 [thread overview]
Message-ID: <jh35og$1fa$1@dough.gmane.org> (raw)
In-Reply-To: <87sjikt1ls.fsf@gmail.com>
On 02/09/2012 11:26 AM, Nicolas Goaziou wrote:
> 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.
> 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?
M. Pinard may want to look into changing the way that glyph displays...
If we were to define a font face which was used for checkboxes, he
could then specify for that font an edited font which displays his
desired checkmark in the character formerly knows as 'X'.
- Allen S. Rout
next prev parent reply other threads:[~2012-02-10 13:23 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
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 [this message]
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='jh35og$1fa$1@dough.gmane.org' \
--to=asr@ufl.edu \
--cc=emacs-orgmode@gnu.org \
/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).