From: David Maus <dmaus@ictsoc.de>
To: Tommy Kelly <tommy.kelly@verilab.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Special properties -- doc buglet?
Date: Sun, 30 Jan 2011 15:50:26 +0100 [thread overview]
Message-ID: <87zkqie98t.wl%dmaus@ictsoc.de> (raw)
In-Reply-To: <m2bp39t7mp.fsf@verilab.com>
[-- Attachment #1.1: Type: text/plain, Size: 848 bytes --]
At Sat, 22 Jan 2011 07:01:18 -0600,
Tommy Kelly wrote:
>
> In section "7.2 Special properties" the current online org manual says:
>
> "The following property names are special and should not be used as keys
> in the properties drawer:
>
> ...
> CATEGORY
> ...
> "
>
>
> Is it correct to have "CATEGORY" in that list? I thought that putting it
> as a key into the property drawer was exactly how to specify categories.
As I see this, listing the CATEGORY property in Chapter 7.2 is okay.
Chapter 7 is about property drawers in general. CATEGORY belongs to
the list of reserved property names with a special meaning to Org.
You should not use this property because it modifies Org mode's
behavior and does not work like any other property.
Best,
-- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena@jabber.org
Email..... dmaus@ictsoc.de
[-- Attachment #1.2: Type: application/pgp-signature, Size: 230 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2011-01-30 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 13:01 Special properties -- doc buglet? Tommy Kelly
2011-01-30 14:50 ` David Maus [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-22 16:22 Tommy Kelly
2011-01-24 8:40 ` Carsten Dominik
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=87zkqie98t.wl%dmaus@ictsoc.de \
--to=dmaus@ictsoc.de \
--cc=emacs-orgmode@gnu.org \
--cc=tommy.kelly@verilab.com \
/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).