Manual typo fixes
This commit is contained in:
parent
c79f5398cc
commit
5bd71d3052
|
@ -9032,20 +9032,16 @@ the estimated effort of an entry (see [[*Effort Estimates]]).
|
||||||
#+vindex: org-agenda-tag-filter-preset
|
#+vindex: org-agenda-tag-filter-preset
|
||||||
#+vindex: org-agenda-effort-filter-preset
|
#+vindex: org-agenda-effort-filter-preset
|
||||||
#+vindex: org-agenda-regexp-filter-preset
|
#+vindex: org-agenda-regexp-filter-preset
|
||||||
Agenda built-in or customized commands are statically defined. Agenda
|
Agenda built-in or custom commands are statically defined. Agenda
|
||||||
filters and limits provide two ways of narrowing down the list of
|
filters and limits provide allow to flexibly narrow down the list of
|
||||||
agenda entries.
|
agenda entries.
|
||||||
|
|
||||||
Filters only change the visibility of items, are very fast and are
|
/Filters/ only change the visibility of items, are very fast and are
|
||||||
mostly used interactively[fn:96]. You can switch quickly between
|
mostly used interactively[fn:96]. You can switch quickly between
|
||||||
different filters without having to recreate the agenda. If creating
|
different filters without having to recreate the agenda. /Limits/ on
|
||||||
the agenda seems slow, one solution would be to create a view that
|
the other hand take effect before the agenda buffer is populated, so
|
||||||
contains everything you might want to work on for a while, and then
|
they are mostly useful when defined as local variables within custom
|
||||||
use filtering to drill down.
|
agenda commands.
|
||||||
|
|
||||||
Limits on the other hand take effect before the agenda buffer is
|
|
||||||
populated, so they are mostly useful when defined as local variables
|
|
||||||
within custom agenda commands.
|
|
||||||
|
|
||||||
**** Filtering in the agenda
|
**** Filtering in the agenda
|
||||||
:PROPERTIES:
|
:PROPERTIES:
|
||||||
|
|
Loading…
Reference in New Issue