org-manual: Undocument `org-fast-tag-selection-include-todo'
* doc/org-manual.org (Fast access to TODO states): Remove references to `org-fast-tag-selection-include-todo' to honour its docstring that discourages using this option. Renumber the footnotes. Link: https://orgmode.org/list/87ttnmw818.fsf@localhost
This commit is contained in:
Ihor Radchenko
parent
6ff0de5c3e
commit
cf7ef80a13
|
|
@ -4111,10 +4111,9 @@ meaning here.]. For example:
|
|||
(sequence "|" "CANCELED(c)")))
|
||||
#+end_src
|
||||
|
||||
#+vindex: org-fast-tag-selection-include-todo
|
||||
If you then press {{{kbd(C-c C-t)}}} followed by the selection key,
|
||||
the entry is switched to this state. {{{kbd(SPC)}}} can be used to
|
||||
remove any TODO keyword from an entry[fn:15].
|
||||
remove any TODO keyword from an entry.
|
||||
|
||||
*** Setting up keywords for individual files
|
||||
:PROPERTIES:
|
||||
|
|
@ -4370,7 +4369,7 @@ example, with the setting
|
|||
You not only define global TODO keywords and fast access keys, but
|
||||
also request that a time is recorded when the entry is set to =DONE=,
|
||||
and that a note is recorded when switching to =WAIT= or
|
||||
=CANCELED=[fn:16]. The setting for =WAIT= is even more special: the
|
||||
=CANCELED=[fn:15]. The setting for =WAIT= is even more special: the
|
||||
=!= after the slash means that in addition to the note taken when
|
||||
entering the state, a timestamp should be recorded when /leaving/ the
|
||||
=WAIT= state, if and only if the /target/ state does not configure
|
||||
|
|
@ -4668,7 +4667,7 @@ of) a large number of subtasks (see [[*Checkboxes]]).
|
|||
#+cindex: checkboxes
|
||||
|
||||
#+vindex: org-list-automatic-rules
|
||||
Every item in a plain list[fn:17] (see [[*Plain Lists]]) can be made into
|
||||
Every item in a plain list[fn:16] (see [[*Plain Lists]]) can be made into
|
||||
a checkbox by starting it with the string =[ ]=. This feature is
|
||||
similar to TODO items (see [[*TODO Items]]), but is more lightweight.
|
||||
Checkboxes are not included into the global TODO list, so they are
|
||||
|
|
@ -5468,7 +5467,7 @@ not be used as keys in the properties drawer:
|
|||
| =PRIORITY= | The priority of the entry, a string with a single letter. |
|
||||
| =SCHEDULED= | The scheduling timestamp. |
|
||||
| =TAGS= | The tags defined directly in the headline. |
|
||||
| =TIMESTAMP= | The first active keyword-less timestamp in the entry.[fn:18] |
|
||||
| =TIMESTAMP= | The first active keyword-less timestamp in the entry.[fn:17] |
|
||||
| =TIMESTAMP_IA= | The first inactive keyword-less timestamp in the entry. |
|
||||
| =TODO= | The TODO keyword of the entry. |
|
||||
|
||||
|
|
@ -5683,7 +5682,7 @@ optional. The individual parts have the following meaning:
|
|||
| =:min= | Smallest time value in column. |
|
||||
| =:max= | Largest time value. |
|
||||
| =:mean= | Arithmetic mean of time values. |
|
||||
| =@min= | Minimum age[fn:19] (in days/hours/mins/seconds). |
|
||||
| =@min= | Minimum age[fn:18] (in days/hours/mins/seconds). |
|
||||
| =@max= | Maximum age (in days/hours/mins/seconds). |
|
||||
| =@mean= | Arithmetic mean of ages (in days/hours/mins/seconds). |
|
||||
| =est+= | Add low-high estimates. |
|
||||
|
|
@ -6050,7 +6049,7 @@ use cases dealing with time and time intervals.
|
|||
|
||||
A timestamp is a specification of a date---possibly with a time or
|
||||
time range---in a special format, either =<2003-09-16 Tue>= or
|
||||
=<2003-09-16 Tue 09:39>= or =<2003-09-16 Tue 12:00-12:30>=[fn:20].
|
||||
=<2003-09-16 Tue 09:39>= or =<2003-09-16 Tue 12:00-12:30>=[fn:19].
|
||||
A timestamp can appear anywhere in the headline or body of an Org tree
|
||||
entry. Its presence causes entries to be shown on specific dates in
|
||||
the agenda (see [[*Weekly/daily agenda]]). We distinguish:
|
||||
|
|
@ -6100,7 +6099,7 @@ the agenda (see [[*Weekly/daily agenda]]). We distinguish:
|
|||
|
||||
For more complex date specifications, Org mode supports using the
|
||||
special expression diary entries implemented in the
|
||||
[[info:emacs#Special Diary Entries][Emacs Calendar package]][fn:21].
|
||||
[[info:emacs#Special Diary Entries][Emacs Calendar package]][fn:20].
|
||||
For example, with optional time:
|
||||
|
||||
#+begin_example
|
||||
|
|
@ -6271,7 +6270,7 @@ a range, it is taken from the stamp in the buffer. When filling in
|
|||
information, Org mode assumes that most of the time you want to enter
|
||||
a date in the future: if you omit the month/year and the given
|
||||
day/month is /before/ today, it assumes that you mean a future
|
||||
date[fn:22]. If the date has been automatically shifted into the
|
||||
date[fn:21]. If the date has been automatically shifted into the
|
||||
future, the time prompt shows this with =(=>F)=.
|
||||
|
||||
For example, let's assume that today is *June 13, 2006*. Here is how
|
||||
|
|
@ -6371,7 +6370,7 @@ from the minibuffer:
|
|||
| {{{kbd(<)}}} | Scroll calendar backward by one month. |
|
||||
| {{{kbd(M-v)}}} | Scroll calendar forward by 3 months. |
|
||||
| {{{kbd(C-v)}}} | Scroll calendar backward by 3 months. |
|
||||
| {{{kbd(C-.)}}} | Select today's date[fn:23] |
|
||||
| {{{kbd(C-.)}}} | Select today's date[fn:22] |
|
||||
|
||||
#+vindex: org-read-date-display-live
|
||||
The actions of the date/time prompt may seem complex, but I assure you
|
||||
|
|
@ -6473,7 +6472,7 @@ immediately after the task they refer to.
|
|||
date.
|
||||
|
||||
#+vindex: org-agenda-skip-scheduled-if-done
|
||||
The headline is listed under the given date[fn:24]. In addition,
|
||||
The headline is listed under the given date[fn:23]. In addition,
|
||||
a reminder that the scheduled date has passed is present in the
|
||||
compilation for /today/, until the entry is marked as done, i.e.,
|
||||
the task is automatically forwarded until completed.
|
||||
|
|
@ -6525,7 +6524,7 @@ expression entry matches.
|
|||
:END:
|
||||
|
||||
The following commands allow you to quickly insert a deadline or to
|
||||
schedule an item:[fn:25]
|
||||
schedule an item:[fn:24]
|
||||
|
||||
- {{{kbd(C-c C-d)}}} (~org-deadline~) ::
|
||||
|
||||
|
|
@ -6591,7 +6590,7 @@ any current timestamp.
|
|||
|
||||
Some tasks need to be repeated again and again. Org mode helps to
|
||||
organize such tasks using a so-called repeater in a =DEADLINE=,
|
||||
=SCHEDULED=, or plain timestamps[fn:26]. In the following example:
|
||||
=SCHEDULED=, or plain timestamps[fn:25]. In the following example:
|
||||
|
||||
#+begin_example
|
||||
,** TODO Pay the rent
|
||||
|
|
@ -6638,7 +6637,7 @@ To mark a task with a repeater as DONE, use {{{kbd(C-- 1 C-c C-t)}}},
|
|||
i.e., ~org-todo~ with a numeric prefix argument of =-1=.
|
||||
|
||||
#+vindex: org-log-repeat
|
||||
A timestamp[fn:27] is added under the deadline, to keep a record that
|
||||
A timestamp[fn:26] is added under the deadline, to keep a record that
|
||||
you actually acted on the previous instance of this deadline.
|
||||
|
||||
As a consequence of shifting the base date, this entry is no longer
|
||||
|
|
@ -6708,7 +6707,7 @@ a project. When you start working on an item, you can start the
|
|||
clock. When you stop working on that task, or when you mark the task
|
||||
done, the clock is stopped and the corresponding time interval is
|
||||
recorded. It also computes the total time spent on each
|
||||
subtree[fn:28] of a project. And it remembers a history or tasks
|
||||
subtree[fn:27] of a project. And it remembers a history or tasks
|
||||
recently clocked, so that you can jump quickly between a number of
|
||||
tasks absorbing your time.
|
||||
|
||||
|
|
@ -7188,7 +7187,7 @@ current clock, or applying it to another one.
|
|||
#+vindex: org-clock-x11idle-program-name
|
||||
By customizing the variable ~org-clock-idle-time~ to some integer,
|
||||
such as 10 or 15, Emacs can alert you when you get back to your
|
||||
computer after being idle for that many minutes[fn:29], and ask what
|
||||
computer after being idle for that many minutes[fn:28], and ask what
|
||||
you want to do with the idle time. There will be a question waiting
|
||||
for you when you get back, indicating how much idle time has passed
|
||||
constantly updated with the current amount, as well as a set of
|
||||
|
|
@ -7981,7 +7980,7 @@ Now lets look at the elements of a template definition. Each entry in
|
|||
|
||||
- =(file+olp+datetree "filename" [ "Level 1 heading" ...])= ::
|
||||
|
||||
This target[fn:30] creates a heading in a date tree[fn:31] for
|
||||
This target[fn:29] creates a heading in a date tree[fn:30] for
|
||||
today's date. If the optional outline path is given, the tree
|
||||
will be built under the node it is pointing to, instead of at top
|
||||
level. Check out the ~:time-prompt~ and ~:tree-type~ properties
|
||||
|
|
@ -8284,7 +8283,7 @@ capture templates in a similar way.]:
|
|||
| | =%:date= (message date header field) |
|
||||
| | =%:date-timestamp= (date as active timestamp) |
|
||||
| | =%:date-timestamp-inactive= (date as inactive timestamp) |
|
||||
| | =%:fromto= (either "to NAME" or "from NAME")[fn:32] |
|
||||
| | =%:fromto= (either "to NAME" or "from NAME")[fn:31] |
|
||||
| gnus | =%:group=, for messages also all email fields |
|
||||
| w3, w3m | =%:url= |
|
||||
| info | =%:file=, =%:node= |
|
||||
|
|
@ -8950,7 +8949,7 @@ a paper agenda, showing all the tasks for the current week or day.
|
|||
#+cindex: org-agenda, command
|
||||
Compile an agenda for the current week from a list of Org files.
|
||||
The agenda shows the entries for each day. With a numeric prefix
|
||||
argument[fn:33]---like {{{kbd(C-u 2 1 M-x org-agenda a)}}}---you may
|
||||
argument[fn:32]---like {{{kbd(C-u 2 1 M-x org-agenda a)}}}---you may
|
||||
set the number of days to be displayed.
|
||||
|
||||
#+vindex: org-agenda-span
|
||||
|
|
@ -9638,7 +9637,7 @@ filters and limits allow to flexibly narrow down the list of agenda
|
|||
entries.
|
||||
|
||||
/Filters/ only change the visibility of items, are very fast and are
|
||||
mostly used interactively[fn:34]. You can switch quickly between
|
||||
mostly used interactively[fn:33]. You can switch quickly between
|
||||
different filters without having to recreate the agenda. /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
|
||||
|
|
@ -10724,7 +10723,7 @@ used for the matching. The example above will therefore define:
|
|||
|
||||
- {{{kbd(x)}}} ::
|
||||
|
||||
as a global search for agenda entries planned[fn:35] this week/day.
|
||||
as a global search for agenda entries planned[fn:34] this week/day.
|
||||
|
||||
- {{{kbd(y)}}} ::
|
||||
|
||||
|
|
@ -10910,7 +10909,7 @@ export custom agenda views as plain text, HTML[fn:: For HTML you need
|
|||
to install Hrvoje Nikšić's =htmlize.el= as an Emacs package from
|
||||
[[https://elpa.nongnu.org/][NonGNU ELPA]] or from
|
||||
[[https://github.com/hniksic/emacs-htmlize][Hrvoje Nikšić's repository]].],
|
||||
Postscript, PDF[fn:36], and iCalendar files. If you
|
||||
Postscript, PDF[fn:35], and iCalendar files. If you
|
||||
want to do this only occasionally, use the following command:
|
||||
|
||||
- {{{kbd(C-x C-w)}}} (~org-agenda-write~) ::
|
||||
|
|
@ -11322,7 +11321,7 @@ converted into dashes, and =...= becomes a compact set of dots.
|
|||
|
||||
Plain ASCII is normally sufficient for almost all note taking.
|
||||
Exceptions include scientific notes, which often require mathematical
|
||||
symbols and the occasional formula. LaTeX[fn:37] is widely used to
|
||||
symbols and the occasional formula. LaTeX[fn:36] is widely used to
|
||||
typeset scientific documents. Org mode supports embedding LaTeX code
|
||||
into its files, because many academics are used to writing and reading
|
||||
LaTeX source code, and because it can be readily processed to produce
|
||||
|
|
@ -11344,7 +11343,7 @@ into images (see [[*Previewing LaTeX fragments]]).
|
|||
LaTeX fragments do not need any special marking at all. The following
|
||||
snippets are identified as LaTeX source code:
|
||||
|
||||
- Environments of any kind[fn:38]. The only requirement is that the
|
||||
- Environments of any kind[fn:37]. The only requirement is that the
|
||||
=\begin= statement appears on a new line, preceded by only
|
||||
whitespace.
|
||||
|
||||
|
|
@ -11393,7 +11392,7 @@ lines:
|
|||
|
||||
#+vindex: org-preview-latex-default-process
|
||||
If you have a working LaTeX installation and =dvipng=, =dvisvgm= or
|
||||
=convert= installed[fn:39], LaTeX fragments can be processed to
|
||||
=convert= installed[fn:38], LaTeX fragments can be processed to
|
||||
produce images of the typeset expressions to be used for inclusion
|
||||
while exporting to HTML (see [[*LaTeX fragments]]), or for inline
|
||||
previewing within Org mode.
|
||||
|
|
@ -11549,9 +11548,9 @@ Here is an example
|
|||
#+vindex: org-latex-src-block-backend
|
||||
If the example is source code from a programming language, or any
|
||||
other text that can be marked up by Font Lock in Emacs, you can ask
|
||||
for the example to look like the fontified Emacs buffer[fn:40]. This
|
||||
for the example to look like the fontified Emacs buffer[fn:39]. This
|
||||
is done with the code block, where you also need to specify the name
|
||||
of the major mode that should be used to fontify the example[fn:41],
|
||||
of the major mode that should be used to fontify the example[fn:40],
|
||||
see [[*Structure Templates]] for shortcuts to easily insert code blocks.
|
||||
|
||||
#+cindex: @samp{BEGIN_SRC}
|
||||
|
|
@ -11817,7 +11816,7 @@ text. Markers always start with =fn:=. For example:
|
|||
#+begin_example
|
||||
The Org website[fn:1] now looks a lot better than it used to.
|
||||
...
|
||||
[fn:50] The link is: https://orgmode.org
|
||||
[fn:49] The link is: https://orgmode.org
|
||||
#+end_example
|
||||
|
||||
Org mode extends the number-based syntax to /named/ footnotes and
|
||||
|
|
@ -12106,7 +12105,7 @@ global variables, include:
|
|||
Language to use for translating certain strings
|
||||
(~org-export-default-language~). With =#+LANGUAGE: fr=, for
|
||||
example, Org translates =Table of contents= to the French =Table des
|
||||
matières=[fn:42].
|
||||
matières=[fn:41].
|
||||
|
||||
- =SELECT_TAGS= ::
|
||||
|
||||
|
|
@ -12406,7 +12405,7 @@ keyword:
|
|||
#+cindex: excluding entries from table of contents
|
||||
#+cindex: table of contents, exclude entries
|
||||
Org includes both numbered and unnumbered headlines in the table of
|
||||
contents[fn:43]. If you need to exclude an unnumbered headline,
|
||||
contents[fn:42]. If you need to exclude an unnumbered headline,
|
||||
along with all its children, set the =UNNUMBERED= property to =notoc=
|
||||
value.
|
||||
|
||||
|
|
@ -12524,7 +12523,7 @@ be omitted to use the obvious defaults.
|
|||
| =#+INCLUDE: "~/.emacs" :lines "10-"= | Include lines from 10 to EOF |
|
||||
|
||||
Inclusions may specify a file-link to extract an object matched by
|
||||
~org-link-search~[fn:44] (see [[*Search Options in File Links]]). The
|
||||
~org-link-search~[fn:43] (see [[*Search Options in File Links]]). The
|
||||
ranges for =:lines= keyword are relative to the requested element.
|
||||
Therefore,
|
||||
|
||||
|
|
@ -12564,7 +12563,7 @@ following syntax:
|
|||
: #+MACRO: name replacement text; $1, $2 are arguments
|
||||
|
||||
#+texinfo: @noindent
|
||||
which can be referenced using ={{{name(arg1, arg2)}}}=[fn:45]. For
|
||||
which can be referenced using ={{{name(arg1, arg2)}}}=[fn:44]. For
|
||||
example
|
||||
|
||||
#+begin_example
|
||||
|
|
@ -12956,7 +12955,7 @@ should in principle be exportable as a Beamer presentation.
|
|||
|
||||
- Org exports a Beamer frame's objects as block environments. Org can
|
||||
enforce wrapping in special block types when =BEAMER_ENV= property
|
||||
is set[fn:46]. For valid values see
|
||||
is set[fn:45]. For valid values see
|
||||
~org-beamer-environments-default~. To add more values, see
|
||||
~org-beamer-environments-extra~.
|
||||
#+vindex: org-beamer-environments-default
|
||||
|
|
@ -13574,7 +13573,7 @@ different ways on HTML pages. The default is to use the
|
|||
with Org[fn:: By default, Org loads MathJax from
|
||||
[[https://www.jsdelivr.com/][jsDelivr]], as recommended in
|
||||
[[https://docs.mathjax.org/en/latest/web/start.html][Getting Started
|
||||
with MathJax Components]].][fn:47]. Some MathJax display options can
|
||||
with MathJax Components]].][fn:46]. Some MathJax display options can
|
||||
be configured via ~org-html-mathjax-options~, or in the buffer. For
|
||||
example, with the following settings,
|
||||
|
||||
|
|
@ -13893,7 +13892,7 @@ LaTeX export backend finds the compiler version to use from
|
|||
Org file. See the docstring for the
|
||||
~org-latex-default-packages-alist~ for loading packages with certain
|
||||
compilers. Also see ~org-latex-bibtex-compiler~ to set the
|
||||
bibliography compiler[fn:48].
|
||||
bibliography compiler[fn:47].
|
||||
|
||||
*** LaTeX specific export settings
|
||||
:PROPERTIES:
|
||||
|
|
@ -18344,7 +18343,7 @@ block, collects the results, and inserts them in the buffer.
|
|||
|
||||
#+cindex: @samp{CALL}, keyword
|
||||
#+vindex: org-babel-inline-result-wrap
|
||||
By calling a named code block[fn:49] from an Org mode buffer or
|
||||
By calling a named code block[fn:48] from an Org mode buffer or
|
||||
a table. Org can call the named code blocks from the current Org mode
|
||||
buffer or from the "Library of Babel" (see [[*Library of Babel]]).
|
||||
|
||||
|
|
@ -18552,7 +18551,7 @@ they are mutually exclusive.
|
|||
|
||||
- =value= ::
|
||||
|
||||
Default for most Babel libraries[fn:49]. Functional mode. Org
|
||||
Default for most Babel libraries[fn:48]. Functional mode. Org
|
||||
gets the value by wrapping the code in a function definition in the
|
||||
language of the source block. That is why when using =:results
|
||||
value=, code should execute like a function and return a value. For
|
||||
|
|
@ -19414,7 +19413,7 @@ the second code block is expanded as
|
|||
#+end_example
|
||||
|
||||
Note that noweb expansion does not automatically carry over =:var=
|
||||
header arguments[fn:50].
|
||||
header arguments[fn:49].
|
||||
|
||||
You may also include the contents of multiple blocks sharing a common
|
||||
=noweb-ref= header argument, which can be set at the file, subtree,
|
||||
|
|
@ -19956,7 +19955,7 @@ in the desired amount with hard spaces and hiding leading stars.
|
|||
To display the buffer in the indented view, activate Org Indent minor
|
||||
mode, using {{{kbd(M-x org-indent-mode)}}}. Text lines that are not
|
||||
headlines are prefixed with virtual spaces to vertically align with
|
||||
the headline text[fn:51].
|
||||
the headline text[fn:50].
|
||||
|
||||
#+vindex: org-indent-indentation-per-level
|
||||
To make more horizontal space, the headlines are shifted by two
|
||||
|
|
@ -19984,7 +19983,7 @@ use =STARTUP= keyword as follows:
|
|||
|
||||
It is possible to use hard spaces to achieve the indentation instead,
|
||||
if the bare ASCII file should have the indented look also outside
|
||||
Emacs[fn:52]. With Org's support, you have to indent all lines to
|
||||
Emacs[fn:51]. With Org's support, you have to indent all lines to
|
||||
line up with the outline headers. You would use these settings[fn::
|
||||
~org-adapt-indentation~ can also be set to ='headline-data=, in which
|
||||
case only data lines below the headline will be indented.]:
|
||||
|
|
@ -21151,7 +21150,7 @@ Tags]]) only for those set in these variables.
|
|||
|
||||
#+vindex: org-mobile-directory
|
||||
The mobile application needs access to a file directory on
|
||||
a server[fn:53] to interact with Emacs. Pass its location through
|
||||
a server[fn:52] to interact with Emacs. Pass its location through
|
||||
the ~org-mobile-directory~ variable. If you can mount that directory
|
||||
locally just set the variable to point to that directory:
|
||||
|
||||
|
|
@ -21195,7 +21194,7 @@ Symbolic links in ~org-directory~ need to have the same name as their
|
|||
targets.].
|
||||
|
||||
Push creates a special Org file =agendas.org= with custom agenda views
|
||||
defined by the user[fn:54].
|
||||
defined by the user[fn:53].
|
||||
|
||||
Finally, Org writes the file =index.org=, containing links to other
|
||||
files. The mobile application reads this file first from the server
|
||||
|
|
@ -21559,7 +21558,7 @@ of these strategies:
|
|||
To wrap a source table in LaTeX, use the =comment= environment
|
||||
provided by =comment.sty=[fn:: https://www.ctan.org/pkg/comment]. To
|
||||
activate it, put ~\usepackage{comment}~ in the document header.
|
||||
Orgtbl mode inserts a radio table skeleton[fn:55] with the command
|
||||
Orgtbl mode inserts a radio table skeleton[fn:54] with the command
|
||||
{{{kbd(M-x orgtbl-insert-radio-table)}}}, which prompts for a table
|
||||
name. For example, if =salesfigures= is the name, the template
|
||||
inserts:
|
||||
|
|
@ -21579,7 +21578,7 @@ The line =#+ORGTBL: SEND= tells Orgtbl mode to use the function
|
|||
~orgtbl-to-latex~ to convert the table to LaTeX format, then insert
|
||||
the table at the target (receive) location named =salesfigures=. Now
|
||||
the table is ready for data entry. It can even use spreadsheet
|
||||
features[fn:56]:
|
||||
features[fn:55]:
|
||||
|
||||
#+begin_example
|
||||
% BEGIN RECEIVE ORGTBL salesfigures
|
||||
|
|
@ -22816,37 +22815,31 @@ from the list of stored links. To keep it in the list for later use,
|
|||
use a triple {{{kbd(C-u)}}} prefix argument to {{{kbd(C-c C-l)}}}, or
|
||||
configure the option ~org-link-keep-stored-after-insertion~.
|
||||
|
||||
[fn:15] Check also the variable ~org-fast-tag-selection-include-todo~,
|
||||
it allows you to change the TODO state through the tags interface (see
|
||||
[[*Setting Tags]]), in case you like to mingle the two concepts. Note
|
||||
that this means you need to come up with unique keys across both sets
|
||||
of keywords.
|
||||
|
||||
[fn:16] It is possible that Org mode records two timestamps when you
|
||||
[fn:15] It is possible that Org mode records two timestamps when you
|
||||
are using both ~org-log-done~ and state change logging. However, it
|
||||
never prompts for two notes: if you have configured both, the state
|
||||
change recording note takes precedence and cancel the closing note.
|
||||
|
||||
[fn:17] With the exception of description lists. But you can allow it
|
||||
[fn:16] With the exception of description lists. But you can allow it
|
||||
by modifying ~org-list-automatic-rules~ accordingly.
|
||||
|
||||
[fn:18] For both =TIMESTAMP= and =TIMESTAMP_IA=: the word "first"
|
||||
[fn:17] For both =TIMESTAMP= and =TIMESTAMP_IA=: the word "first"
|
||||
refers to the first occurrence in the entry, not the earliest in time;
|
||||
the prefix =CLOCK:= at the beginning of a clock entry is considered a
|
||||
keyword in this context; and timestamps inside property drawers are
|
||||
ignored.
|
||||
|
||||
[fn:19] An age can be defined as a duration, using units defined in
|
||||
[fn:18] An age can be defined as a duration, using units defined in
|
||||
~org-duration-units~, e.g., =3d 1h=. If any value in the column is as
|
||||
such, the summary is also expressed as a duration.
|
||||
|
||||
[fn:20] The Org date format is inspired by the standard ISO 8601
|
||||
[fn:19] The Org date format is inspired by the standard ISO 8601
|
||||
date/time format. To use an alternative format, see [[*Custom time
|
||||
format]]. The day name is optional when you type the date yourself.
|
||||
However, any date inserted or modified by Org adds that day name, for
|
||||
reading convenience.
|
||||
|
||||
[fn:21] When working with the standard diary expression functions, you
|
||||
[fn:20] When working with the standard diary expression functions, you
|
||||
need to be very careful with the order of the arguments. That order
|
||||
depends evilly on the variable ~calendar-date-style~. For example, to
|
||||
specify a date December 1, 2005, the call might look like
|
||||
|
|
@ -22859,35 +22852,35 @@ functions, but with stable ISO order of arguments (year, month, day)
|
|||
wherever applicable, independent of the value of
|
||||
~calendar-date-style~.
|
||||
|
||||
[fn:22] See the variable ~org-read-date-prefer-future~. You may set
|
||||
[fn:21] See the variable ~org-read-date-prefer-future~. You may set
|
||||
that variable to the symbol ~time~ to even make a time before now
|
||||
shift the date to tomorrow.
|
||||
|
||||
[fn:23] You can also use the calendar command {{{kbd(.)}}} to jump to
|
||||
[fn:22] You can also use the calendar command {{{kbd(.)}}} to jump to
|
||||
today's date, but if you are inserting an hour specification for your
|
||||
timestamp, {{{kbd(.)}}} will then insert a dot after the hour. By contrast,
|
||||
{{{kbd(C-.)}}} will always jump to today's date.
|
||||
|
||||
[fn:24] It will still be listed on that date after it has been marked
|
||||
[fn:23] It will still be listed on that date after it has been marked
|
||||
as done. If you do not like this, set the variable
|
||||
~org-agenda-skip-scheduled-if-done~.
|
||||
|
||||
[fn:25] The =SCHEDULED= and =DEADLINE= dates are inserted on the line
|
||||
[fn:24] The =SCHEDULED= and =DEADLINE= dates are inserted on the line
|
||||
right below the headline. Do not put any text between this line and
|
||||
the headline.
|
||||
|
||||
[fn:26] Org does not repeat inactive timestamps, however. See
|
||||
[fn:25] Org does not repeat inactive timestamps, however. See
|
||||
[[*Timestamps]].
|
||||
|
||||
[fn:27] You can change this using the option ~org-log-repeat~, or the
|
||||
[fn:26] You can change this using the option ~org-log-repeat~, or the
|
||||
=STARTUP= options =logrepeat=, =lognoterepeat=, and =nologrepeat=.
|
||||
With =lognoterepeat=, you will also be prompted for a note.
|
||||
|
||||
[fn:28] Clocking only works if all headings are indented with less
|
||||
[fn:27] Clocking only works if all headings are indented with less
|
||||
than 30 stars. This is a hard-coded limitation of ~lmax~ in
|
||||
~org-clock-sum~.
|
||||
|
||||
[fn:29] On computers using macOS, idleness is based on actual user
|
||||
[fn:28] On computers using macOS, idleness is based on actual user
|
||||
idleness, not just Emacs' idle time. For X11, you can install a
|
||||
utility program =x11idle.c=, available in the =org-contrib/=
|
||||
repository, or install the xprintidle package and set it to the
|
||||
|
|
@ -22895,13 +22888,13 @@ variable ~org-clock-x11idle-program-name~ if you are running Debian,
|
|||
to get the same general treatment of idleness. On other systems, idle
|
||||
time refers to Emacs idle time only.
|
||||
|
||||
[fn:30] Org used to offer four different targets for date/week tree
|
||||
[fn:29] Org used to offer four different targets for date/week tree
|
||||
capture. Now, Org automatically translates these to use
|
||||
~file+olp+datetree~, applying the ~:time-prompt~ and ~:tree-type~
|
||||
properties. Please rewrite your date/week-tree targets using
|
||||
~file+olp+datetree~ since the older targets are now deprecated.
|
||||
|
||||
[fn:31] A date tree is an outline structure with years on the highest
|
||||
[fn:30] A date tree is an outline structure with years on the highest
|
||||
level, months or ISO weeks as sublevels and then dates on the lowest
|
||||
level.
|
||||
|
||||
|
|
@ -22915,15 +22908,15 @@ level.
|
|||
TODO state, priority, tags, statistics cookies, and COMMENT keywords
|
||||
are allowed in the tree structure.
|
||||
|
||||
[fn:32] This is always the other, not the user. See the variable
|
||||
[fn:31] This is always the other, not the user. See the variable
|
||||
~org-link-from-user-regexp~.
|
||||
|
||||
[fn:33] For backward compatibility, the universal prefix argument
|
||||
[fn:32] For backward compatibility, the universal prefix argument
|
||||
{{{kbd(C-u)}}} causes all TODO entries to be listed before the agenda.
|
||||
This feature is deprecated, use the dedicated TODO list, or a block
|
||||
agenda instead (see [[*Block agenda]]).
|
||||
|
||||
[fn:34] Custom agenda commands can preset a filter by binding one of
|
||||
[fn:33] Custom agenda commands can preset a filter by binding one of
|
||||
the variables ~org-agenda-tag-filter-preset~,
|
||||
~org-agenda-category-filter-preset~, ~org-agenda-effort-filter-preset~
|
||||
or ~org-agenda-regexp-filter-preset~ as an option. This filter is
|
||||
|
|
@ -22933,72 +22926,72 @@ property of the entire agenda view---in a block agenda, you should
|
|||
only set this in the global options section, not in the section of an
|
||||
individual block.
|
||||
|
||||
[fn:35] /Planned/ means here that these entries have some planning
|
||||
[fn:34] /Planned/ means here that these entries have some planning
|
||||
information attached to them, like a timestamp, a scheduled or
|
||||
a deadline string. See ~org-agenda-entry-types~ on how to set what
|
||||
planning information is taken into account.
|
||||
|
||||
[fn:36] To create PDF output, the Ghostscript ps2pdf utility must be
|
||||
[fn:35] To create PDF output, the Ghostscript ps2pdf utility must be
|
||||
installed on the system. Selecting a PDF file also creates the
|
||||
postscript file.
|
||||
|
||||
[fn:37] LaTeX is a macro system based on Donald\nbsp{}E.\nbsp{}Knuth's TeX
|
||||
[fn:36] LaTeX is a macro system based on Donald\nbsp{}E.\nbsp{}Knuth's TeX
|
||||
system. Many of the features described here as "LaTeX" are really
|
||||
from TeX, but for simplicity I am blurring this distinction.
|
||||
|
||||
[fn:38] When MathJax is used, only the environments recognized by
|
||||
[fn:37] When MathJax is used, only the environments recognized by
|
||||
MathJax are processed. When dvipng, dvisvgm, or ImageMagick suite is
|
||||
used to create images, any LaTeX environment is handled.
|
||||
|
||||
[fn:39] These are respectively available at
|
||||
[fn:38] These are respectively available at
|
||||
[[https://sourceforge.net/projects/dvipng/]], [[http://dvisvgm.bplaced.net/]]
|
||||
and from the ImageMagick suite. Choose the converter by setting the
|
||||
variable ~org-preview-latex-default-process~ accordingly.
|
||||
|
||||
[fn:40] This works automatically for the HTML backend (it requires
|
||||
[fn:39] This works automatically for the HTML backend (it requires
|
||||
version 1.34 of the =htmlize.el= package, which you need to install).
|
||||
Fontified code chunks in LaTeX can be achieved using either the
|
||||
[[https://www.ctan.org/pkg/listings][listings]] LaTeX package, [[https://www.ctan.org/pkg/minted][minted]] LaTeX package, or by using
|
||||
[[https://elpa.gnu.org/packages/engrave-faces.html][engrave-faces]] . Refer to ~org-latex-src-block-backend~ for details.
|
||||
|
||||
[fn:41] Source code in code blocks may also be evaluated either
|
||||
[fn:40] Source code in code blocks may also be evaluated either
|
||||
interactively or on export. See [[*Working with Source Code]] for more
|
||||
information on evaluating code blocks.
|
||||
|
||||
[fn:42] For export to LaTeX format---or LaTeX-related formats such as
|
||||
[fn:41] For export to LaTeX format---or LaTeX-related formats such as
|
||||
Beamer---, the =org-latex-package-alist= variable needs further
|
||||
configuration. See [[LaTeX specific export settings]].
|
||||
|
||||
[fn:43] At the moment, some export backends do not obey this
|
||||
[fn:42] At the moment, some export backends do not obey this
|
||||
specification. For example, LaTeX export excludes every unnumbered
|
||||
headline from the table of contents.
|
||||
|
||||
[fn:44] Note that ~org-link-search-must-match-exact-headline~ is
|
||||
[fn:43] Note that ~org-link-search-must-match-exact-headline~ is
|
||||
locally bound to non-~nil~. Therefore, ~org-link-search~ only matches
|
||||
headlines and named elements.
|
||||
|
||||
[fn:45] Since commas separate the arguments, commas within arguments
|
||||
[fn:44] Since commas separate the arguments, commas within arguments
|
||||
have to be escaped with the backslash character. So only those
|
||||
backslash characters before a comma need escaping with another
|
||||
backslash character.
|
||||
|
||||
[fn:46] If =BEAMER_ENV= is set, Org export adds =B_environment= tag
|
||||
[fn:45] If =BEAMER_ENV= is set, Org export adds =B_environment= tag
|
||||
to make it visible. The tag serves as a visual aid and has no
|
||||
semantic relevance.
|
||||
|
||||
[fn:47] Please note that exported formulas are part of an HTML
|
||||
[fn:46] Please note that exported formulas are part of an HTML
|
||||
document, and that signs such as =<=, =>=, or =&= have special
|
||||
meanings. See [[https://docs.mathjax.org/en/latest/input/tex/html.html#tex-and-latex-in-html-documents][MathJax TeX and LaTeX in HTML documents]].
|
||||
|
||||
[fn:48] This does not allow setting different bibliography compilers
|
||||
[fn:47] This does not allow setting different bibliography compilers
|
||||
for different files. However, "smart" LaTeX compilation systems, such
|
||||
as latexmk, can select the correct bibliography compiler.
|
||||
|
||||
[fn:49] Actually, the constructs =call_<name>()= and =src_<lang>{}=
|
||||
[fn:48] Actually, the constructs =call_<name>()= and =src_<lang>{}=
|
||||
are not evaluated when they appear in a keyword (see [[*Summary of
|
||||
In-Buffer Settings]]).
|
||||
|
||||
[fn:50] In the following example, attempting to evaluate
|
||||
[fn:49] In the following example, attempting to evaluate
|
||||
the second code block will give an error, because the variables
|
||||
defined in the first code block will not be defined in the second
|
||||
block.
|
||||
|
|
@ -23026,29 +23019,29 @@ values.
|
|||
,#+END_SRC
|
||||
#+end_example
|
||||
|
||||
[fn:51] Org Indent mode also sets ~wrap-prefix~ correctly for
|
||||
[fn:50] Org Indent mode also sets ~wrap-prefix~ correctly for
|
||||
indenting and wrapping long lines of headlines or text. This minor
|
||||
mode also handles Visual Line mode and directly applied settings
|
||||
through ~word-wrap~.
|
||||
|
||||
[fn:52] This works, but requires extra effort. Org Indent mode is
|
||||
[fn:51] This works, but requires extra effort. Org Indent mode is
|
||||
more convenient for most applications.
|
||||
|
||||
[fn:53] For a server to host files, consider using a WebDAV server,
|
||||
[fn:52] For a server to host files, consider using a WebDAV server,
|
||||
such as [[https://nextcloud.com][Nextcloud]]. Additional help is at this [[https://orgmode.org/worg/org-faq.html#mobileorg_webdav][FAQ entry]].
|
||||
|
||||
[fn:54] While creating the agendas, Org mode forces =ID= properties
|
||||
[fn:53] While creating the agendas, Org mode forces =ID= properties
|
||||
on all referenced entries, so that these entries can be uniquely
|
||||
identified if Org Mobile flags them for further action. To avoid
|
||||
setting properties configure the variable
|
||||
~org-mobile-force-id-on-agenda-items~ to ~nil~. Org mode then relies
|
||||
on outline paths, assuming they are unique.
|
||||
|
||||
[fn:55] By default this works only for LaTeX, HTML, and Texinfo.
|
||||
[fn:54] By default this works only for LaTeX, HTML, and Texinfo.
|
||||
Configure the variable ~orgtbl-radio-table-templates~ to install
|
||||
templates for other modes.
|
||||
|
||||
[fn:56] If the =TBLFM= keyword contains an odd number of dollar
|
||||
[fn:55] If the =TBLFM= keyword contains an odd number of dollar
|
||||
characters, this may cause problems with Font Lock in LaTeX mode. As
|
||||
shown in the example you can fix this by adding an extra line inside
|
||||
the =comment= environment that is used to balance the dollar
|
||||
|
|
|
|||
Loading…
Reference in New Issue