ndwarshuis
/
org-mode
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

org.texi: Small fixes 

* doc/org.texi (Matching tags and properties): Fix typo.  Remove
  inaccurate paragraph.
This commit is contained in:
Nicolas Goaziou 2014-12-06 21:30:59 +01:00
parent db078f4764
commit 4c172fe5cc
1 changed files with 2 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/org.texi
View File

@ -8126,8 +8126,8 @@ the entry. The ITEM special property cannot currently be used in tags/property
searches@footnote{But @pxref{x-agenda-skip-entry-regexp,
,skipping entries based on regexp}.}.
In addition to the @pxref{Special properties}, one other ``property'' can
also be used. @code{LEVEL} represents the level of an entry. So a search
In addition to the @ref{Special properties}, one other ``property'' can also
be used. @code{LEVEL} represents the level of an entry. So a search
@samp{+LEVEL=3+boss-TODO="DONE"} lists all level three headlines that have
the tag @samp{boss} and are @emph{not} marked with the TODO keyword DONE@.
In buffers with @code{org-odd-levels-only} set, @samp{LEVEL} does not count
@ -8185,11 +8185,6 @@ property that is numerically smaller than 2, a @samp{:With:} property that is
matched by the regular expression @samp{Sarah\|Denny}, and that are scheduled
on or after October 11, 2008.
Accessing TODO, LEVEL, and CATEGORY during a search is fast. Accessing any
other properties will slow down the search. However, once you have paid the
price by accessing one property, testing additional properties is cheap
again.
You can configure Org mode to use property inheritance during a search, but
beware that this can slow down searches considerably. See @ref{Property
inheritance}, for details.