From 8def68b7238154fa52cab2d9f3b6708f8695a5c5 Mon Sep 17 00:00:00 2001 From: Nicolas Goaziou Date: Sat, 19 May 2018 13:49:48 +0200 Subject: [PATCH] org-manual: Document `org-complete-tags-always-offer-all-agenda-tags' * doc/org-manual.org (Setting Tags): Document `org-complete-tags-always-offer-all-agenda-tags'. --- doc/org-manual.org | 393 +++++++++++++++++++++++---------------------- 1 file changed, 199 insertions(+), 194 deletions(-) diff --git a/doc/org-manual.org b/doc/org-manual.org index 93f6c0d7d..51884ec99 100644 --- a/doc/org-manual.org +++ b/doc/org-manual.org @@ -4672,14 +4672,15 @@ also a special command for inserting tags: When the cursor is in a headline, this does the same as {{{kbd(C-c C-q)}}}. +#+vindex: org-complete-tags-always-offer-all-agenda-tags #+vindex: org-tag-alist +#+cindex: @samp{TAGS}, keyword Org supports tag insertion based on a /list of tags/. By default this list is constructed dynamically, containing all tags currently used in -the buffer. You may also globally specify a hard list of tags with -the variable ~org-tag-alist~. Finally you can set the default tags -for a given file with lines like +the buffer[fn:54]. You may also globally specify a hard list of tags +with the variable ~org-tag-alist~. Finally you can set the default +tags for a given file using the =TAGS= keyword, like -#+cindex: @samp{TAGS}, keyword #+begin_example ,#+TAGS: @work @home @tennisclub ,#+TAGS: laptop car pc sailboat @@ -4767,7 +4768,7 @@ by the following configuration: If at least one tag has a selection key then pressing {{{kbd(C-c C-c)}}} automatically presents you with a special interface, listing inherited tags, the tags of the current headline, and a list of all -valid tags with corresponding keys[fn:54]. +valid tags with corresponding keys[fn:55]. Pressing keys assigned to tags adds or removes them from the list of tags in the current line. Selecting a tag in a group of mutually @@ -5403,7 +5404,7 @@ optional. The individual parts have the following meaning: - {{{var(SUMMARY-TYPE)}}} :: The summary type. If specified, the column values for parent - nodes are computed from the children[fn:55]. + nodes are computed from the children[fn:56]. Supported summary types are: @@ -5420,7 +5421,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:56] (in days/hours/mins/seconds). | + | =@min= | Minimum age[fn:57] (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. | @@ -5449,7 +5450,7 @@ contrast, =est+= estimates the full job more realistically, at 10--15 days. Here is an example for a complete columns definition, along with -allowed values[fn:57]. +allowed values[fn:58]. #+begin_example :COLUMNS: %25ITEM %9Approved(Approved?){X} %Owner %11Status \ @@ -5701,7 +5702,7 @@ recalculated automatically after an update. An alternative way to capture and process property values into a table is provided by Eric Schulte's =org-collector.el= which is -a contributed package[fn:58]. It provides a general API to collect +a contributed package[fn:59]. It provides a general API to collect properties from entries in a certain scope, and arbitrary Lisp expressions to process these values before inserting them into a table or a dynamic block. @@ -5735,7 +5736,7 @@ is used in a much wider sense. A timestamp is a specification of a date (possibly with a time or a range of times) 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:59]. +=<2003-09-16 Tue 09:39>= or =<2003-09-16 Tue 12:00-12:30>=[fn:60]. 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: @@ -5775,7 +5776,7 @@ the agenda (see [[*Weekly/daily agenda]]). We distinguish: #+cindex: sexp timestamps For more complex date specifications, Org mode supports using the special sexp diary entries implemented in the Emacs - calendar/diary package[fn:60]. For example, with optional time: + calendar/diary package[fn:61]. For example, with optional time: #+begin_example ,* 22:00-23:00 The nerd meeting on every 2nd Thursday of the month @@ -5929,7 +5930,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:61]. If the date has been automatically shifted into the +date[fn:62]. 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 @@ -5991,7 +5992,7 @@ separator in the latter case, e.g.: #+cindex: calendar, for selecting date #+vindex: org-popup-calendar-for-date-prompt -Parallel to the minibuffer prompt, a calendar is popped up[fn:62]. +Parallel to the minibuffer prompt, a calendar is popped up[fn:63]. When you exit the date prompt, either by clicking on a date in the calendar, or by pressing {{{kbd(RET)}}}, the date selected in the calendar is combined with the information entered at the prompt. You @@ -6028,7 +6029,7 @@ The actions of the date/time prompt may seem complex, but I assure you they will grow on you, and you will start getting annoyed by pretty much any other way of entering a date/time out there. To help you understand what is going on, the current interpretation of your input -is displayed live in the minibuffer[fn:63]. +is displayed live in the minibuffer[fn:64]. *** Custom time format :PROPERTIES: @@ -6121,7 +6122,7 @@ immediately after the task they refer to. given date. #+vindex: org-agenda-skip-scheduled-if-done - The headline is listed under the given date[fn:64]. In addition, + The headline is listed under the given date[fn:65]. In addition, a reminder that the scheduled date has passed is present in the compilation for /today/, until the entry is marked DONE, i.e., the task is automatically forwarded until completed. @@ -6173,7 +6174,7 @@ S-exp entry matches. :END: The following commands allow you to quickly insert a deadline or to -schedule an item:[fn:65] +schedule an item:[fn:66] - {{{kbd(C-c C-d)}}} (~org-deadline~) :: @@ -6185,7 +6186,7 @@ schedule an item:[fn:65] =CLOSED= timestamp . When called with a prefix argument, also remove any existing deadline from the entry. Depending on the variable ~org-log-redeadline~, take a note when changing an - existing deadline[fn:66]. + existing deadline[fn:67]. - {{{kbd(C-c C-s)}}} (~org-schedule~) :: @@ -6197,7 +6198,7 @@ schedule an item:[fn:65] =CLOSED= timestamp. When called with a prefix argument, also remove the scheduling date from the entry. Depending on the variable ~org-log-reschedule~, take a note when changing an - existing scheduling time[fn:67]. + existing scheduling time[fn:68]. - {{{kbd(C-c C-x C-k)}}} (~org-mark-entry-for-agenda-action~) :: @@ -6276,7 +6277,7 @@ then also the /next/ instance of the repeated entry will not be active. Org mode deals with this in the following way: when you try to mark such an entry DONE, using {{{kbd(C-c C-t)}}}, it shifts the base date of the repeating timestamp by the repeater interval, and -immediately sets the entry state back to TODO[fn:68]. In the example +immediately sets the entry state back to TODO[fn:69]. In the example above, setting the state to DONE would actually switch the date like this: @@ -6289,7 +6290,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:69] is added under the deadline, to keep a record that +A timestamp[fn:70] 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 @@ -6355,7 +6356,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:70] of a project. And it remembers a history or tasks +subtree[fn:71] of a project. And it remembers a history or tasks recently clocked, to that you can jump quickly between a number of tasks absorbing your time. @@ -6368,7 +6369,7 @@ To save the clock history across Emacs sessions, use: #+vindex: org-clock-persist When you clock into a new task after resuming Emacs, the incomplete -clock[fn:71] is retrieved (see [[*Resolving idle time]]) and you are +clock[fn:72] is retrieved (see [[*Resolving idle time]]) and you are prompted about what to do with it. *** Clocking commands @@ -6408,14 +6409,14 @@ prompted about what to do with it. time shown is all time ever clocked for this task and its children. If the task has an effort estimate (see [[*Effort Estimates]]), the mode line displays the current clocking time - against it[fn:72]. If the task is a repeating one (see [[*Repeated + against it[fn:73]. If the task is a repeating one (see [[*Repeated tasks]]), show only the time since the last reset of the - task[fn:73]. You can exercise more control over show time with + task[fn:74]. You can exercise more control over show time with the =CLOCK_MODELINE_TOTAL= property. It may have the values =current= to show only the current clocking instance, =today= to show all time clocked on this tasks today---see also the variable ~org-extend-today-until~, ~all~ to include all time, or - ~auto~ which is the default[fn:74]. Clicking with + ~auto~ which is the default[fn:75]. Clicking with {{{kbd(mouse-1)}}} onto the mode line entry pops up a menu with clocking options. @@ -6429,7 +6430,7 @@ prompted about what to do with it. directly computes the resulting time in inserts it after the time range as ==>HH:MM=. See the variable ~org-log-note-clock-out~ for the possibility to record an additional note together with - the clock-out timestamp[fn:75]. + the clock-out timestamp[fn:76]. - {{{kbd(C-c C-x C-x)}}} (~org-clock-in-last~) :: @@ -6683,7 +6684,7 @@ using the =:formatter= parameter. - :lang :: - Language[fn:76] to use for descriptive cells like "Task". + Language[fn:77] to use for descriptive cells like "Task". - :link :: @@ -6758,7 +6759,7 @@ day, you could write: #+end_example #+texinfo: @noindent -To use a specific time range you could write[fn:77] +To use a specific time range you could write[fn:78] #+begin_example ,#+BEGIN: clocktable :tstart "<2006-08-10 Thu 10:00>" @@ -6811,7 +6812,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:78], and ask what +computer after being idle for that many minutes[fn:79], 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 @@ -6957,7 +6958,7 @@ displayed. #+vindex: org-agenda-columns-add-appointments-to-effort-sum If you switch to column view in the daily/weekly agenda, the effort -column summarizes the estimated work effort for each day[fn:79], and +column summarizes the estimated work effort for each day[fn:80], and you can use this to find space in your schedule. To get an overview of the entire part of the day that is committed, you can set the option ~org-agenda-columns-add-appointments-to-effort-sum~. The @@ -7309,7 +7310,7 @@ Now lets look at the elements of a template definition. Each entry in - =(file+olp+datetree "filename" [ "Level 1 heading" ...])= :: - This target[fn:80] creates a heading in a date tree[fn:81] for + This target[fn:81] creates a heading in a date tree[fn:82] 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~ @@ -7412,7 +7413,7 @@ Now lets look at the elements of a template definition. Each entry in :DESCRIPTION: Filling in information about time and context. :END: -In the template itself, special "%-escapes"[fn:82] allow dynamic +In the template itself, special "%-escapes"[fn:83] allow dynamic insertion of content. The templates are expanded in the order given here: @@ -7535,7 +7536,7 @@ here: #+texinfo: @noindent #+vindex: org-store-link-props -For specific link types, the following keywords are defined[fn:83]: +For specific link types, the following keywords are defined[fn:84]: #+vindex: org-from-is-user-regexp | Link type | Available keywords | @@ -7548,7 +7549,7 @@ For specific link types, the following keywords are defined[fn:83]: | | ~%: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:84] | +| | ~%:fromto~ (either "to NAME" or "from NAME")[fn:85] | | gnus | ~%:group~, for messages also all email fields | | w3, w3m | ~%:url~ | | info | ~%:file~, ~%:node~ | @@ -7598,7 +7599,7 @@ Another method is /attachments/, which are files located in a directory belonging to an outline node. Org uses directories named by the unique ID of each entry. These directories are located in the ~data~ directory which lives in the same directory where your Org file -lives[fn:85]. If you initialize this directory with =git init=, Org +lives[fn:86]. If you initialize this directory with =git init=, Org automatically commits changes when it sees them. The attachment system has been contributed to Org by John Wiegley. @@ -8019,7 +8020,7 @@ special command: ~org-outline-path-complete-in-steps~. If you would like to be able to create new nodes as new parents for refiling on the fly, check the variable ~org-refile-allow-creating-parent-nodes~. - When the variable ~org-log-refile~[fn:86] is set, a timestamp or + When the variable ~org-log-refile~[fn:87] is set, a timestamp or a note is recorded whenever an entry is refiled. - {{{kbd(C-u C-c C-w)}}} :: @@ -8284,12 +8285,12 @@ the window configuration is restored when the agenda exits: #+vindex: org-agenda-files The information to be shown is normally collected from all /agenda -files/, the files listed in the variable ~org-agenda-files~[fn:87]. +files/, the files listed in the variable ~org-agenda-files~[fn:88]. If a directory is part of this list, all files with the extension =.org= in this directory are part of the list. Thus, even if you only work with a single Org file, that file should -be put into the list[fn:88]. You can customize ~org-agenda-files~, +be put into the list[fn:89]. You can customize ~org-agenda-files~, but the easiest way to maintain it is through the following commands #+attr_texinfo: :sep and @@ -8423,7 +8424,7 @@ commands: - {{{kbd(<)}}} :: #+kindex: < @r{(Agenda dispatcher)} - Restrict an agenda command to the current buffer[fn:89]. After + Restrict an agenda command to the current buffer[fn:90]. After pressing {{{kbd(<)}}}, you still need to press the character selecting the command. @@ -8432,7 +8433,7 @@ commands: #+kindex: < < @r{(Agenda dispatcher)} If there is an active region, restrict the following agenda command to the region. Otherwise, restrict it to the current - subtree[fn:90]. After pressing {{{kbd(< <)}}}, you still need to + subtree[fn:91]. After pressing {{{kbd(< <)}}}, you still need to press the character selecting the command. - {{{kbd(*)}}} :: @@ -8483,7 +8484,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:91]---like {{{kbd(C-u 2 1 M-x org-agenda a)}}}---you + argument[fn:92]---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 @@ -8542,7 +8543,7 @@ the entries into an Org file. Org mode evaluates diary-style sexp entries, and does it faster because there is no overhead for first creating the diary display. Note that the sexp entries must start at the left margin, no whitespace is allowed before them, as seen in the -following segment of an Org file:[fn:92] +following segment of an Org file:[fn:93] #+begin_example ,* Holidays @@ -9049,7 +9050,7 @@ Time ranges can be specified with two timestamps: #+vindex: org-agenda-search-headline-for-time In the headline of the entry itself, a time(range)---like =12:45= or -a =8:30-1pm=---may also appear as plain text[fn:93]. +a =8:30-1pm=---may also appear as plain text[fn:94]. If the agenda integrates the Emacs diary (see [[*Weekly/daily agenda]]), time specifications in diary entries are recognized as well. @@ -9158,7 +9159,7 @@ custom agenda commands. estimates. The difference between this and a custom agenda command is that filtering is very fast, so that you can switch quickly between different filters without having to recreate the - agenda.[fn:94] + agenda.[fn:95] You are prompted for a tag selection letter; {{{kbd(SPC)}}} means any tag at all. Pressing {{{kbd(TAB)}}} at that prompt offers @@ -9587,7 +9588,7 @@ the other commands, the cursor needs to be in the desired line. with the variable ~org-agenda-start-with-clockreport-mode~. By using a prefix argument when toggling this mode (i.e., {{{kbd(C-u R)}}}), the clock table does not show contributions from entries - that are hidden by agenda filtering[fn:95]. See also the + that are hidden by agenda filtering[fn:96]. See also the variable ~org-clock-report-include-clocking-task~. - {{{kbd(v c)}}} :: @@ -10025,7 +10026,7 @@ the other commands, the cursor needs to be in the desired line. - {{{kbd(f)}}} :: #+vindex: org-agenda-bulk-custom-functions - Apply a function[fn:96] to marked entries. For example, the + Apply a function[fn:97] to marked entries. For example, the function below sets the =CATEGORY= property of the entries to =web=. @@ -10066,7 +10067,7 @@ the other commands, the cursor needs to be in the desired line. #+cindex: diary entries, creating from agenda Insert a new entry into the diary, using the date at the cursor and (for block entries) the date at the mark. This adds to the - Emacs diary file[fn:97], in a way similar to the {{{kbd(i)}}} + Emacs diary file[fn:98], in a way similar to the {{{kbd(i)}}} command in the calendar. The diary file pops up in another window, where you can add the entry. @@ -10194,13 +10195,13 @@ after the dispatcher command in order to access the command. Usually this will be just a single character, but if you have many similar commands, you can also define two-letter combinations where the first character is the same in several combinations and serves as a prefix -key[fn:98]. The second parameter is the search type, followed by the +key[fn:99]. The second parameter is the search type, followed by the string or regular expression to be used for the matching. The example above will therefore define: - {{{kbd(x)}}} :: - as a global search for agenda entries planned[fn:99] this + as a global search for agenda entries planned[fn:100] this week/day. - {{{kbd(y)}}} :: @@ -10382,8 +10383,8 @@ See the docstring of the variable for more information. If you are away from your computer, it can be very useful to have a printed version of some agenda views to carry around. Org mode can -export custom agenda views as plain text, HTML[fn:100], Postscript, -PDF[fn:101], and iCalendar files. If you want to do this only +export custom agenda views as plain text, HTML[fn:101], Postscript, +PDF[fn:102], and iCalendar files. If you want to do this only occasionally, use the following command: - {{{kbd(C-x C-w)}}} (~org-agenda-write~) :: @@ -10397,7 +10398,7 @@ occasionally, use the following command: If you need to export certain agenda views frequently, you can associate any custom agenda command with a list of output file -names[fn:102]. Here is an example that first defines custom commands +names[fn:103]. Here is an example that first defines custom commands for the agenda and the global TODO list, together with a number of files to which to export them. Then we define two block agenda commands and specify file names for them as well. File names can be @@ -10486,7 +10487,7 @@ emacs -eval (org-batch-store-agenda-views) -kill #+end_src #+texinfo: @noindent -or, if you need to modify some parameters[fn:103] +or, if you need to modify some parameters[fn:104] #+begin_src shell emacs -eval '(org-batch-store-agenda-views \ @@ -10752,9 +10753,9 @@ Here is an example #+vindex: org-latex-listings 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:104]. This +for the example to look like the fontified Emacs buffer[fn:105]. 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:105], +of the major mode that should be used to fontify the example[fn:106], see [[*Structure Templates]] for shortcuts to easily insert code blocks. #+cindex: @samp{BEGIN_SRC} @@ -10795,7 +10796,7 @@ In HTML, hovering the mouse over such a link remote-highlights the corresponding code line, which is kind of cool. You can also add a =-r= switch which /removes/ the labels from the -source code[fn:106]. With the =-n= switch, links to these references +source code[fn:107]. With the =-n= switch, links to these references are labeled by the line numbers from the code listing. Otherwise links use the labels with no parentheses. Here is an example: @@ -10833,10 +10834,10 @@ a shortcut is provided (see [[*Structure Templates]]). #+findex: org-edit-special Edit the source code example at point in its native mode. This works by switching to a temporary buffer with the source code. - You need to exit by pressing {{{kbd(C-c ')}}} again[fn:107]. The + You need to exit by pressing {{{kbd(C-c ')}}} again[fn:108]. The edited version then replaces the old version in the Org buffer. Fixed-width regions---where each line starts with a colon - followed by a space---are edited using ~artist-mode~[fn:108] to + followed by a space---are edited using ~artist-mode~[fn:109] to allow creating ASCII drawings easily. Using this command in an empty line creates a new fixed-width region. @@ -10890,7 +10891,7 @@ document, e.g., =\under{}not underlined\under= exports as =_not underlined_=. #+cindex: special symbols, in-buffer display If you would like to see entities displayed as UTF-8 characters, use -the following command[fn:109]: +the following command[fn:110]: - {{{kbd(C-c C-x \)}}} (~org-toggle-pretty-entities~) :: #+kindex: C-c C-x \ @@ -10904,7 +10905,7 @@ the following command[fn:109]: #+cindex: dash, special symbol #+cindex: ellipsis, special symbol In addition to regular entities defined above, Org exports in -a special way[fn:110] the following commonly used character +a special way[fn:111] the following commonly used character combinations: =\-= is treated as a shy hyphen, =--= and =---= are converted into dashes, and =...= becomes a compact set of dots. @@ -10948,7 +10949,7 @@ change this convention. For example, when setting this variable to 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:111] is widely used to +symbols and the occasional formula. LaTeX[fn:112] 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 @@ -10970,7 +10971,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:112]. The only requirement is that the +- Environments of any kind[fn:113]. The only requirement is that the =\begin= statement appears on a new line, preceded by only whitespace. @@ -11014,7 +11015,7 @@ lines: #+vindex: org-preview-latex-default-process If you have a working LaTeX installation and =dvipng=, =dvisvgm= or -=convert= installed[fn:113], LaTeX fragments can be processed to +=convert= installed[fn:114], 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. @@ -11083,7 +11084,7 @@ more details see the documentation of CDLaTeX mode): #+kindex: TAB The {{{kbd(TAB)}}} key expands the template if the cursor is - inside a LaTeX fragment[fn:114]. For example, {{{kbd(TAB)}}} + inside a LaTeX fragment[fn:115]. For example, {{{kbd(TAB)}}} expands =fr= to =\frac{}{}= and position the cursor correctly inside the first brace. Another {{{kbd(TAB)}}} gets you into the second brace. @@ -11298,7 +11299,7 @@ global variables, include: #+cindex: @samp{DATE}, keyword #+vindex: org-export-date-timestamp-format - A date or a time-stamp[fn:115]. + A date or a time-stamp[fn:116]. - =EMAIL= :: @@ -11593,7 +11594,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:116]. If you need to exclude an unnumbered headline, +contents[fn:117]. If you need to exclude an unnumbered headline, along with all its children, set the =UNNUMBERED= property to =notoc= value. @@ -11711,7 +11712,7 @@ following syntax: : #+MACRO: name replacement text; $1, $2 are arguments #+texinfo: @noindent -which can be referenced using ={{{name(arg1, arg2)}}}=[fn:117]. For +which can be referenced using ={{{name(arg1, arg2)}}}=[fn:118]. For example #+begin_example @@ -11830,7 +11831,7 @@ are not exported. Finally, a =COMMENT= keyword at the beginning of an entry, but after any other keyword or priority cookie, comments out the entire subtree. In this case, the subtree is not exported and no code block within it -is executed either[fn:118]. The command below helps changing the +is executed either[fn:119]. The command below helps changing the comment status of a headline. - {{{kbd(C-c ;)}}} (~org-toggle-comment~) :: @@ -12101,7 +12102,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:119]. For valid values see + is set[fn:120]. For valid values see ~org-beamer-environments-default~. To add more values, see ~org-beamer-environments-extra~. #+vindex: org-beamer-environments-default @@ -12677,7 +12678,7 @@ is. #+vindex: org-html-mathjax-options~ LaTeX math snippets (see [[*LaTeX fragments]]) can be displayed in two different ways on HTML pages. The default is to use the [[http://www.mathjax.org][MathJax]], -which should work out of the box with Org[fn:120]. Some MathJax +which should work out of the box with Org[fn:121]. Some MathJax display options can be configured via ~org-html-mathjax-options~, or in the buffer. For example, with the following settings, @@ -12689,7 +12690,7 @@ in the buffer. For example, with the following settings, #+texinfo: @noindent equation labels are displayed on the left margin and equations are five em from the left margin. In addition, it loads the two MathJax -extensions =cancel.js= and =noErrors.js=[fn:121]. +extensions =cancel.js= and =noErrors.js=[fn:122]. #+vindex: org-html-mathjax-template See the docstring of ~org-html-mathjax-options~ for all supported @@ -12752,7 +12753,7 @@ line. #+vindex: org-export-html-todo-kwd-class-prefix #+vindex: org-export-html-tag-class-prefix You can modify the CSS style definitions for the exported file. The -HTML exporter assigns the following special CSS classes[fn:122] to +HTML exporter assigns the following special CSS classes[fn:123] to appropriate parts of the document---your style specifications may change these, in addition to any of the standard classes like for headlines, tables, etc. @@ -12992,7 +12993,7 @@ LaTeX export back-end 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:123]. +bibliography compiler[fn:124]. *** LaTeX specific export settings :PROPERTIES: @@ -13602,7 +13603,7 @@ a limit to a level before the absolute limit (see [[*Export Settings]]). The ODT export back-end handles creating of OpenDocument Text (ODT) format. Documents created by this exporter use the -{{{cite(OpenDocument-v1.2 specification)}}}[fn:124] and are compatible +{{{cite(OpenDocument-v1.2 specification)}}}[fn:125] and are compatible with LibreOffice 3.4. *** Pre-requisites for ODT export @@ -14003,7 +14004,7 @@ document in one of the following ways: variables ~org-latex-to-mathml-convert-command~ and ~org-latex-to-mathml-jar-file~. - If you prefer to use MathToWeb[fn:125] as your converter, you can + If you prefer to use MathToWeb[fn:126] as your converter, you can configure the above variables as shown below. #+begin_src emacs-lisp @@ -14013,7 +14014,7 @@ document in one of the following ways: "/path/to/mathtoweb.jar") #+end_src - To use LaTeX​ML[fn:126] use + To use LaTeX​ML[fn:127] use #+begin_src emacs-lisp (setq org-latex-to-mathml-convert-command @@ -14333,7 +14334,7 @@ with the =#+ATTR_ODT= line. For a discussion on default formatting of tables, see [[*Tables in ODT export]]. This feature closely mimics the way table templates are defined in the -OpenDocument-v1.2 specification.[fn:127] +OpenDocument-v1.2 specification.[fn:128] #+vindex: org-odt-table-styles For quick preview of this feature, install the settings below and export the @@ -14367,7 +14368,7 @@ templates, define new styles there. To use this feature proceed as follows: -1. Create a table template[fn:128]. +1. Create a table template[fn:129]. A table template is set of =table-cell= and =paragraph= styles for each of the following table cell categories: @@ -14406,7 +14407,7 @@ To use this feature proceed as follows: == element of the content template file (see [[x-orgodtcontenttemplate-xml][Factory styles]]). -2. Define a table style[fn:129]. +2. Define a table style[fn:130]. #+vindex: org-odt-table-styles To define a table style, create an entry for the style in the @@ -15433,7 +15434,7 @@ If you want to publish the Org file as an =.org= file but with ~org-publish-org-to-org~. This produces =file.org= and put it in the publishing directory. If you want a htmlized version of this file, set the parameter ~:htmlized-source~ to ~t~. It produces -=file.org.html= in the publishing directory[fn:130]. +=file.org.html= in the publishing directory[fn:131]. Other files like images only need to be copied to the publishing destination; for this you can use ~org-publish-attachment~. For @@ -16810,13 +16811,13 @@ See [[*Languages]] to enable other languages. #+kindex: C-c C-v e #+findex: org-babel-execute-src-block Org provides many ways to execute code blocks. {{{kbd(C-c C-c)}}} or -{{{kbd(C-c C-v e)}}} with the point on a code block[fn:131] calls the +{{{kbd(C-c C-v e)}}} with the point on a code block[fn:132] calls the ~org-babel-execute-src-block~ function, which executes the code in the 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:132] from an Org mode buffer or +By calling a named code block[fn:133] 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]]). @@ -17754,7 +17755,7 @@ for Python and Emacs Lisp languages. #+cindex: syntax, Noweb #+cindex: source code, Noweb reference -Org supports named blocks in Noweb[fn:133] style syntax: +Org supports named blocks in Noweb[fn:134] style syntax: : <> @@ -18254,7 +18255,7 @@ Org Tempo expands snippets to structures defined in ~org-structure-template-alist~ and ~org-tempo-keywords-alist~. For example, {{{kbd(< s TAB)}}} creates a code block. Enable it by customizing ~org-modules~ or add ~(require 'org-tempo)~ to your Emacs -init file[fn:134]. +init file[fn:135]. #+attr_texinfo: :columns 0.1 0.9 @@ -18510,7 +18511,7 @@ changes. #+vindex: org-startup-indented Dynamic virtual indentation is controlled by the variable - ~org-startup-indented~.[fn:135] + ~org-startup-indented~.[fn:136] - =indent= :: @@ -18842,7 +18843,7 @@ uses only one star and indents text to line with the heading: #+findex: org-indent-mode To turn this mode on, use the minor mode, ~org-indent-mode~. Text lines that are not headlines are prefixed with spaces to vertically -align with the headline text[fn:136]. +align with the headline text[fn:137]. #+vindex: org-indent-indentation-per-level To make more horizontal space, the headlines are shifted by two stars. @@ -18877,7 +18878,7 @@ headings as shown in examples below. #+vindex: org-adapt-indentation Org supports this with paragraph filling, line wrapping, and structure editing, preserving or adapting the indentation as - appropriate[fn:137]. + appropriate[fn:138]. - /Hiding leading stars/ :: @@ -18911,7 +18912,7 @@ headings as shown in examples below. #+vindex: org-odd-levels-only Using stars for only odd levels, 1, 3, 5, ..., can also clean up - the clutter. This removes two stars from each level[fn:138]. + the clutter. This removes two stars from each level[fn:139]. For Org to properly handle this cleaner structure during edits and exports, configure the variable ~org-odd-levels-only~. To set this per-file, use either one of the following lines: @@ -19489,9 +19490,9 @@ of these strategies: #+cindex: @LaTeX{}, and Orgtbl mode To wrap a source table in LaTeX, use the =comment= environment -provided by =comment.sty=[fn:139]. To activate it, put +provided by =comment.sty=[fn:140]. To activate it, put ~\usepackage{comment}~ in the document header. Orgtbl mode inserts -a radio table skeleton[fn:138] with the command {{{kbd(M-x +a radio table skeleton[fn:139] 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: @@ -19510,7 +19511,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:140]: +features[fn:141]: #+begin_example % BEGIN RECEIVE ORGTBL salesfigures @@ -19725,7 +19726,7 @@ Dynamic blocks, like any other block, can be narrowed with #+vindex: org-agenda-skip-function #+vindex: org-agenda-skip-function-global Org provides a special hook to further limit items in agenda views: -~agenda~, ~agenda*~[fn:141], ~todo~, ~alltodo~, ~tags~, ~tags-todo~, +~agenda~, ~agenda*~[fn:142], ~todo~, ~alltodo~, ~tags~, ~tags-todo~, ~tags-tree~. Specify a custom function that tests inclusion of every matched item in the view. This function can also skip as much as is needed. @@ -19768,7 +19769,7 @@ meaningful string suitable for the agenda view. #+vindex: org-agenda-skip-function Search for entries with a limit set on levels for the custom search. This is a general approach to creating custom searches in Org. To -include all levels, use =LEVEL>0=[fn:142]. Then to selectively pick +include all levels, use =LEVEL>0=[fn:143]. Then to selectively pick the matched entries, use ~org-agenda-skip-function~, which also accepts Lisp forms, such as ~org-agenda-skip-entry-if~ and ~org-agenda-skip-subtree-if~. For example: @@ -20263,13 +20264,13 @@ with Emacs. With a public server, consider encrypting the files. MobileOrg version 1.5 supports encryption for the iPhone. Org also requires =openssl= installed on the local computer. To turn on encryption, set the same password in MobileOrg and in Emacs. Set the -password in the variable ~org-mobile-use-encryption~[fn:143]. Note +password in the variable ~org-mobile-use-encryption~[fn:144]. Note that even after MobileOrg encrypts the file contents, the file name remains visible on the file systems of the local computer, the server, and the mobile device. For a server to host files, consider options like [[http://dropbox.com][Dropbox.com]] -account[fn:144]. On first connection, MobileOrg creates a directory +account[fn:145]. On first connection, MobileOrg creates a directory =MobileOrg= on Dropbox. Pass its location to Emacs through an initialisation file variable as follows: @@ -20291,15 +20292,15 @@ Org pushes files listed in ~org-mobile-files~ to ~org-mobile-directory~. Files include agenda files (as listed in ~org-agenda-files~). Customize ~org-mobile-files~ to add other files. File names are staged with paths relative to ~org-directory~, so all -files should be inside this directory[fn:145]. +files should be inside this directory[fn:146]. Push creates a special Org file =agendas.org= with custom agenda views -defined by the user[fn:146]. +defined by the user[fn:147]. Finally, Org writes the file =index.org=, containing links to other files. MobileOrg reads this file first from the server to determine what other files to download for agendas. For faster downloads, -MobileOrg only reads files whose checksums[fn:147] have changed. +MobileOrg only reads files whose checksums[fn:148] have changed. ** Pulling from MobileOrg :PROPERTIES: @@ -20313,7 +20314,7 @@ Org integrates its data in an inbox file format. 1. #+vindex: org-mobile-inbox-for-pull - Org moves all entries found in =mobileorg.org=[fn:148] and appends + Org moves all entries found in =mobileorg.org=[fn:149] and appends them to the file pointed to by the variable ~org-mobile-inbox-for-pull~. Each captured entry and each editing event is a top-level entry in the inbox file. @@ -21016,30 +21017,34 @@ C-c)}}} activates any changes in the line. [fn:53] This is only true if the search does not involve more complex tests including properties (see [[*Property Searches]]). -[fn:54] Keys are automatically assigned to tags that have no +[fn:54] To extend this default list to all tags used in all agenda +files (see [[*Agenda Views]]), customize the variable +~org-complete-tags-always-offer-all-agenda-tags~. + +[fn:55] Keys are automatically assigned to tags that have no configured keys. -[fn:55] If more than one summary type applies to the same property, +[fn:56] If more than one summary type applies to the same property, the parent values are computed according to the first of them. -[fn:56] An age is defined as a duration, using effort modifiers +[fn:57] An age is defined as a duration, using effort modifiers defined in ~org-effort-durations~, e.g., =3d 1h=. If any value in the column is as such, the summary is also an effort duration. -[fn:57] Please note that the =COLUMNS= definition must be on a single +[fn:58] Please note that the =COLUMNS= definition must be on a single line; it is wrapped here only because of formatting constraints. -[fn:58] Contributed packages are not part of Emacs, but are +[fn:59] Contributed packages are not part of Emacs, but are distributed with the main distribution of Org---visit [[https://orgmode.org]]. -[fn:59] The Org date format is inspired by the standard ISO 8601 +[fn:60] 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:60] When working with the standard diary sexp functions, you need +[fn:61] When working with the standard diary sexp 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 12, 2005, the call might look like @@ -21051,64 +21056,64 @@ like the corresponding ~diary-~ functions, but with stable ISO order of arguments (year, month, day) wherever applicable, independent of the value of ~calendar-date-style~. -[fn:61] See the variable ~org-read-date-prefer-future~. You may set +[fn:62] 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:62] If you do not need/want the calendar, configure the variable +[fn:63] If you do not need/want the calendar, configure the variable ~org-popup-calendar-for-date-prompt~. -[fn:63] If you find this distracting, turn off the display with +[fn:64] If you find this distracting, turn off the display with ~org-read-date-display-live~. -[fn:64] It will still be listed on that date after it has been marked +[fn:65] It will still be listed on that date after it has been marked DONE. If you do not like this, set the variable ~org-agenda-skip-scheduled-if-done~. -[fn:65] The =SCHEDULED= and =DEADLINE= dates are inserted on the line +[fn:66] 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:66] Note the corresponding =STARTUP= options =logredeadline=, +[fn:67] Note the corresponding =STARTUP= options =logredeadline=, =lognoteredeadline=, and =nologredeadline=. -[fn:67] Note the corresponding =STARTUP= options =logreschedule=, +[fn:68] Note the corresponding =STARTUP= options =logreschedule=, =lognotereschedule=, and =nologreschedule=. -[fn:68] In fact, the target state is taken from, in this sequence, the +[fn:69] In fact, the target state is taken from, in this sequence, the =REPEAT_TO_STATE= property, the variable ~org-todo-repeat-to-state~ if it is a string, the previous TODO state if ~org-todo-repeat-to-state~ is ~t~, or the first state of the TODO state sequence. -[fn:69] You can change this using the option ~org-log-repeat~, or the +[fn:70] 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:70] Clocking only works if all headings are indented with less +[fn:71] 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:71] To resume the clock under the assumption that you have worked +[fn:72] To resume the clock under the assumption that you have worked on this task while outside Emacs, use ~(setq org-clock-persist t)~. -[fn:72] To add an effort estimate "on the fly", hook a function doing +[fn:73] To add an effort estimate "on the fly", hook a function doing this to ~org-clock-in-prepare-hook~. -[fn:73] The last reset of the task is recorded by the =LAST_REPEAT= +[fn:74] The last reset of the task is recorded by the =LAST_REPEAT= property. -[fn:74] See also the variable ~org-clock-mode-line-total~. +[fn:75] See also the variable ~org-clock-mode-line-total~. -[fn:75] The corresponding in-buffer setting is: =#+STARTUP: +[fn:76] The corresponding in-buffer setting is: =#+STARTUP: lognoteclock-out=. -[fn:76] Language terms can be set through the variable +[fn:77] Language terms can be set through the variable ~org-clock-clocktable-language-setup~. -[fn:77] Note that all parameters must be specified in a single +[fn:78] Note that all parameters must be specified in a single line---the line is broken here only to fit it into the manual. -[fn:78] On computers using macOS, idleness is based on actual user +[fn:79] 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 =contrib/scripts/= directory of the Org Git distribution, or install the xprintidle @@ -21116,232 +21121,232 @@ package and set it to the 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:79] Please note the pitfalls of summing hierarchical data in +[fn:80] Please note the pitfalls of summing hierarchical data in a flat list ([[*Using Column View in the Agenda]]). -[fn:80] Org used to offer four different targets for date/week tree +[fn:81] 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:81] A date tree is an outline structure with years on the highest +[fn:82] 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. Tags are allowed in the tree structure. -[fn:82] If you need one of these sequences literally, escape the =%= +[fn:83] If you need one of these sequences literally, escape the =%= with a backslash. -[fn:83] If you define your own link types (see [[*Adding Hyperlink +[fn:84] If you define your own link types (see [[*Adding Hyperlink Types]]), any property you store with ~org-store-link-props~ can be accessed in capture templates in a similar way. -[fn:84] This is always the other, not the user. See the variable +[fn:85] This is always the other, not the user. See the variable ~org-from-is-user-regexp~. -[fn:85] If you move entries or Org files from one directory to +[fn:86] If you move entries or Org files from one directory to another, you may want to configure ~org-attach-directory~ to contain an absolute path. -[fn:86] Note the corresponding =STARTUP= options =logrefile=, +[fn:87] Note the corresponding =STARTUP= options =logrefile=, =lognoterefile=, and =nologrefile=. -[fn:87] If the value of that variable is not a list, but a single file +[fn:88] If the value of that variable is not a list, but a single file name, then the list of agenda files in maintained in that external file. -[fn:88] When using the dispatcher, pressing {{{kbd(<)}}} before +[fn:89] When using the dispatcher, pressing {{{kbd(<)}}} before selecting a command actually limits the command to the current file, and ignores ~org-agenda-files~ until the next dispatcher command. -[fn:89] For backward compatibility, you can also press {{{kbd(1)}}} to +[fn:90] For backward compatibility, you can also press {{{kbd(1)}}} to restrict to the current buffer. -[fn:90] For backward compatibility, you can also press {{{kbd(0)}}} to +[fn:91] For backward compatibility, you can also press {{{kbd(0)}}} to restrict to the current region/subtree. -[fn:91] For backward compatibility, the universal prefix argument +[fn:92] 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:92] The variable ~org-anniversary~ used in the example is just +[fn:93] The variable ~org-anniversary~ used in the example is just like ~diary-anniversary~, but the argument order is always according to ISO and therefore independent of the value of ~calendar-date-style~. -[fn:93] You can, however, disable this by setting +[fn:94] You can, however, disable this by setting ~org-agenda-search-headline-for-time~ variable to a ~nil~ value. -[fn:94] Custom commands can preset a filter by binding the variable +[fn:95] Custom commands can preset a filter by binding the variable ~org-agenda-tag-filter-preset~ as an option. This filter is then applied to the view and persists as a basic filter through refreshes and more secondary filtering. The filter is a global 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:95] Only tags filtering is respected here, effort filtering is +[fn:96] Only tags filtering is respected here, effort filtering is ignored. -[fn:96] You can also create persistent custom functions through +[fn:97] You can also create persistent custom functions through ~org-agenda-bulk-custom-functions~. -[fn:97] This file is parsed for the agenda when +[fn:98] This file is parsed for the agenda when ~org-agenda-include-diary~ is set. -[fn:98] You can provide a description for a prefix key by inserting +[fn:99] You can provide a description for a prefix key by inserting a cons cell with the prefix and the description. -[fn:99] /Planned/ means here that these entries have some planning +[fn:100] /Planned/ means here that these entries have some planning information attached to them, like a time-stamp, a scheduled or a deadline string. See ~org-agenda-entry-types~ on how to set what planning information is taken into account. -[fn:100] For HTML you need to install Hrvoje Niksic's =htmlize.el= +[fn:101] For HTML you need to install Hrvoje Niksic's =htmlize.el= from [[https://github.com/hniksic/emacs-htmlize][Hrvoje Niksic's repository]]. -[fn:101] To create PDF output, the Ghostscript ps2pdf utility must be +[fn:102] To create PDF output, the Ghostscript ps2pdf utility must be installed on the system. Selecting a PDF file also creates the postscript file. -[fn:102] If you want to store standard views like the weekly agenda or +[fn:103] If you want to store standard views like the weekly agenda or the global TODO list as well, you need to define custom commands for them in order to be able to specify file names. -[fn:103] Quoting depends on the system you use, please check the FAQ +[fn:104] Quoting depends on the system you use, please check the FAQ for examples. -[fn:104] This works automatically for the HTML backend (it requires +[fn:105] 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 listings package or the [[https://github.com/gpoore/minted][minted]] package. Refer to ~org-export-latex-listings~ for details. -[fn:105] Source code in code blocks may also be evaluated either +[fn:106] 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:106] Adding =-k= to =-n -r= /keeps/ the labels in the source code +[fn:107] Adding =-k= to =-n -r= /keeps/ the labels in the source code while using line numbers for the links, which might be useful to explain those in an Org mode example code. -[fn:107] Upon exit, lines starting with =*=, =,*=, =#+= and =,#+= get +[fn:108] Upon exit, lines starting with =*=, =,*=, =#+= and =,#+= get a comma prepended, to keep them from being interpreted by Org as outline nodes or special syntax. These commas are stripped when editing with {{{kbd(C-c ')}}}, and also before export. -[fn:108] You may select a different-mode with the variable +[fn:109] You may select a different-mode with the variable ~org-edit-fixed-width-region-mode~. -[fn:109] You can turn this on by default by setting the variable +[fn:110] You can turn this on by default by setting the variable ~org-pretty-entities~, or on a per-file base with the =STARTUP= option =entitiespretty=. -[fn:110] This behavior can be disabled with =-= export setting (see +[fn:111] This behavior can be disabled with =-= export setting (see [[*Export Settings]]). -[fn:111] LaTeX is a macro system based on Donald\nbsp{}E.\nbsp{}Knuth's TeX +[fn:112] 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:112] When MathJax is used, only the environments recognized by +[fn:113] 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:113] These are respectively available at +[fn:114] These are respectively available at [[http://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:114] Org mode has a method to test if the cursor is inside such +[fn:115] Org mode has a method to test if the cursor is inside such a fragment, see the documentation of the function ~org-inside-LaTeX-fragment-p~. -[fn:115] The variable ~org-export-date-timestamp-format~ defines how +[fn:116] The variable ~org-export-date-timestamp-format~ defines how this timestamp are exported. -[fn:116] At the moment, some export back-ends do not obey this +[fn:117] At the moment, some export back-ends do not obey this specification. For example, LaTeX export excludes every unnumbered headline from the table of contents. -[fn:117] Since commas separate the arguments, commas within arguments +[fn:118] 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:118] For a less drastic behavior, consider using a select tag (see +[fn:119] For a less drastic behavior, consider using a select tag (see [[*Export Settings]]) instead. -[fn:119] If =BEAMER_ENV= is set, Org export adds =B_environment= tag +[fn:120] 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:120] By default Org loads MathJax from [[https://cdnjs.com][cdnjs.com]] as recommended by +[fn:121] By default Org loads MathJax from [[https://cdnjs.com][cdnjs.com]] as recommended by [[http://www.mathjax.org][MathJax]]. -[fn:121] See [[http://docs.mathjax.org/en/latest/tex.html#tex-extensions][TeX and LaTeX extensions]] in the [[http://docs.mathjax.org][MathJax manual]] to learn +[fn:122] See [[http://docs.mathjax.org/en/latest/tex.html#tex-extensions][TeX and LaTeX extensions]] in the [[http://docs.mathjax.org][MathJax manual]] to learn about extensions. -[fn:122] If the classes on TODO keywords and tags lead to conflicts, +[fn:123] If the classes on TODO keywords and tags lead to conflicts, use the variables ~org-html-todo-kwd-class-prefix~ and ~org-html-tag-class-prefix~ to make them unique. -[fn:123] This does not allow setting different bibliography compilers +[fn:124] 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:124] See [[http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.html][Open Document Format for Office Applications +[fn:125] See [[http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.html][Open Document Format for Office Applications (OpenDocument) Version 1.2]]. -[fn:125] See [[http://www.mathtoweb.com/cgi-bin/mathtoweb_home.pl][MathToWeb]]. +[fn:126] See [[http://www.mathtoweb.com/cgi-bin/mathtoweb_home.pl][MathToWeb]]. -[fn:126] See [[http://dlmf.nist.gov/LaTeXML/]]. +[fn:127] See [[http://dlmf.nist.gov/LaTeXML/]]. -[fn:127] [[http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.html][OpenDocument-v1.2 Specification]] +[fn:128] [[http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.html][OpenDocument-v1.2 Specification]] -[fn:128] See the == element of the +[fn:129] See the == element of the OpenDocument-v1.2 specification. -[fn:129] See the attributes =table:template-name=, +[fn:130] See the attributes =table:template-name=, =table:use-first-row-styles=, =table:use-last-row-styles=, =table:use-first-column-styles=, =table:use-last-column-styles=, =table:use-banding-rows-styles=, and =table:use-banding-column-styles= of the == element in the OpenDocument-v1.2 specification. -[fn:130] If the publishing directory is the same as the source +[fn:131] If the publishing directory is the same as the source directory, =file.org= is exported as =file.org.org=, so you probably do not want to do this. -[fn:131] The option ~org-babel-no-eval-on-ctrl-c-ctrl-c~ can be used +[fn:132] The option ~org-babel-no-eval-on-ctrl-c-ctrl-c~ can be used to remove code evaluation from the {{{kbd(C-c C-c)}}} key binding. -[fn:132] Actually, the constructs =call_()= and =src_{}= +[fn:133] Actually, the constructs =call_()= and =src_{}= are not evaluated when they appear in a keyword line---i.e. lines starting with =#+KEYWORD:=, see [[*Summary of In-Buffer Settings]]. -[fn:133] For Noweb literate programming details, see +[fn:134] For Noweb literate programming details, see http://www.cs.tufts.edu/~nr/noweb/. -[fn:134] For more information, please refer to the commentary section +[fn:135] For more information, please refer to the commentary section in =org-tempo.el=. -[fn:135] Note that ~org-indent-mode~ also sets the ~wrap-prefix~ +[fn:136] Note that ~org-indent-mode~ also sets the ~wrap-prefix~ property, such that ~visual-line-mode~ (or purely setting ~word-wrap~) wraps long lines (including headlines) correctly indented. -[fn:136] The ~org-indent-mode~ also sets the ~wrap-prefix~ correctly +[fn:137] The ~org-indent-mode~ also sets the ~wrap-prefix~ correctly for indenting and wrapping long lines of headlines or text. This minor mode handles ~visual-line-mode~ and directly applied settings through ~word-wrap~. -[fn:137] Also see the variable ~org-adapt-indentation~. +[fn:138] Also see the variable ~org-adapt-indentation~. -[fn:138] Because =LEVEL=2= has 3 stars, =LEVEL=3= has 4 stars, and so +[fn:139] Because =LEVEL=2= has 3 stars, =LEVEL=3= has 4 stars, and so on. -[fn:139] https://ctan.org/tex-archive/macros/latex/contrib/comment?lang=en +[fn:140] https://ctan.org/tex-archive/macros/latex/contrib/comment?lang=en -[fn:140] If the =TBLFM= keyword contains an odd number of dollar +[fn:141] 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 @@ -21349,32 +21354,32 @@ expressions. If you are using AUCTeX with the font-latex library, a much better solution is to add the =comment= environment to the variable ~LaTeX-verbatim-environments~. -[fn:141] The ~agenda*~ view is the same as ~agenda~ except that it +[fn:142] The ~agenda*~ view is the same as ~agenda~ except that it only considers /appointments/, i.e., scheduled and deadline items that have a time specification =[h]h:mm= in their time-stamps. -[fn:142] Note that, for ~org-odd-levels-only~, a level number +[fn:143] Note that, for ~org-odd-levels-only~, a level number corresponds to order in the hierarchy, not to the number of stars. -[fn:143] If Emacs is configured for safe storing of passwords, then +[fn:144] If Emacs is configured for safe storing of passwords, then configure the variable, ~org-mobile-encryption-password~; please read the docstring of that variable. -[fn:144] An alternative is to use a WebDAV server. MobileOrg +[fn:145] An alternative is to use a WebDAV server. MobileOrg documentation has details of WebDAV server configuration. Additional help is at this [[https://orgmode.org/worg/org-faq.html#mobileorg_webdav][FAQ entry]]. -[fn:145] Symbolic links in ~org-directory~ need to have the same name +[fn:146] Symbolic links in ~org-directory~ need to have the same name as their targets. -[fn:146] While creating the agendas, Org mode forces ID properties on +[fn:147] While creating the agendas, Org mode forces ID properties on all referenced entries, so that these entries can be uniquely identified if MobileOrg 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:147] Checksums are stored automatically in the file +[fn:148] Checksums are stored automatically in the file =checksums.dat=. -[fn:148] The file will be empty after this operation. +[fn:149] The file will be empty after this operation.