From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Manual does not mention LEVEL special property
Date: Mon, 15 Apr 2019 14:23:23 -0400 [thread overview]
Message-ID: <87k1fv9lgk.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: 87imvfqnqw.fsf@nicolasgoaziou.fr
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Hello,
>
> Omari Norman <omari@smileystation.com> writes:
>
>> The Org mode manual does not mention the LEVEL special property; can you
>> please add it?
>>
>> https://orgmode.org/manual/Special-properties.html
>
> I don't think LEVEL is a special property. Why do you think it should be
> one?
>
The "Matching tags and properties" section seems to imply that:
,----
| You may also test for properties (see Properties and Columns) at the
| same time as matching tags. The properties may be real properties, or
| special properties that represent other metadata (see Special
| Properties). For example, the property ‘TODO’ represents the TODO
| keyword of the entry. Or, the property ‘LEVEL’ represents the level of
| an entry. So searching ‘+LEVEL=3+boss-TODO="DONE"’ lists all level
| three headlines that have the tag ‘boss’ and are not marked with the
| TODO keyword ‘DONE’. In buffers with org-odd-levels-only set, ‘LEVEL’
| does not count the number of stars, but ‘LEVEL=2’ corresponds to 3
| stars etc.
`----
AFAIU, special properties are properties of a headline, even though
the user has not defined them (indeed, *should not* define them) in a
properties drawer. If that's so, I think LEVEL qualifies as a special
property.
--
Nick
"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler
prev parent reply other threads:[~2019-04-15 18:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-14 14:34 Manual does not mention LEVEL special property Omari Norman
2019-04-15 15:41 ` Nicolas Goaziou
2019-04-15 18:23 ` Nick Dokos [this message]
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=87k1fv9lgk.fsf@alphaville.usersys.redhat.com \
--to=ndokos@gmail.com \
--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).