forked from mirrors/org-mode
Merge branch 'maint'
This commit is contained in:
commit
9410fbe060
|
@ -6043,26 +6043,26 @@ can control the calendar fully from the minibuffer:
|
|||
#+kindex: .
|
||||
#+kindex: C-.
|
||||
#+attr_texinfo: :columns 0.25 0.55
|
||||
| {{{kbd(RET)}}} | Choose date at point in calendar. |
|
||||
| {{{kbd(mouse-1)}}} | Select date by clicking on it. |
|
||||
| {{{kbd(S-RIGHT)}}} | One day forward. |
|
||||
| {{{kbd(S-LEFT)}}} | One day backward. |
|
||||
| {{{kbd(S-DOWN)}}} | One week forward. |
|
||||
| {{{kbd(S-UP)}}} | One week backward. |
|
||||
| {{{kbd(M-S-RIGHT)}}} | One month forward. |
|
||||
| {{{kbd(M-S-LEFT)}}} | One month backward. |
|
||||
| {{{kbd(>)}}} | Scroll calendar forward by one month. |
|
||||
| {{{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(.)}}} or {{{kbd(C-.)}}} | Select today's date |
|
||||
| {{{kbd(RET)}}} | Choose date at point in calendar. |
|
||||
| {{{kbd(mouse-1)}}} | Select date by clicking on it. |
|
||||
| {{{kbd(S-RIGHT)}}} | One day forward. |
|
||||
| {{{kbd(S-LEFT)}}} | One day backward. |
|
||||
| {{{kbd(S-DOWN)}}} | One week forward. |
|
||||
| {{{kbd(S-UP)}}} | One week backward. |
|
||||
| {{{kbd(M-S-RIGHT)}}} | One month forward. |
|
||||
| {{{kbd(M-S-LEFT)}}} | One month backward. |
|
||||
| {{{kbd(>)}}} | Scroll calendar forward by one month. |
|
||||
| {{{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:63] |
|
||||
|
||||
#+vindex: org-read-date-display-live
|
||||
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:
|
||||
|
@ -6154,7 +6154,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: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 as done, i.e.,
|
||||
the task is automatically forwarded until completed.
|
||||
|
@ -6206,7 +6206,7 @@ expression 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~) ::
|
||||
|
||||
|
@ -6218,7 +6218,7 @@ schedule an item:[fn:65]
|
|||
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].
|
||||
deadline[fn:67].
|
||||
|
||||
- {{{kbd(C-c C-s)}}} (~org-schedule~) ::
|
||||
|
||||
|
@ -6230,7 +6230,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].
|
||||
scheduling time[fn:68].
|
||||
|
||||
- {{{kbd(C-c / d)}}} (~org-check-deadlines~) ::
|
||||
|
||||
|
@ -6270,7 +6270,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:68]. In the following example:
|
||||
=SCHEDULED=, or plain timestamps[fn:69]. In the following example:
|
||||
|
||||
#+begin_example
|
||||
,** TODO Pay the rent
|
||||
|
@ -6298,7 +6298,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 as 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:69]. In the example
|
||||
immediately sets the entry state back to TODO[fn:70]. In the example
|
||||
above, setting the state to =DONE= would actually switch the date like
|
||||
this:
|
||||
|
||||
|
@ -6311,7 +6311,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:70] is added under the deadline, to keep a record that
|
||||
A timestamp[fn:71] 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
|
||||
|
@ -6381,7 +6381,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:71] of a project. And it remembers a history or tasks
|
||||
subtree[fn:72] 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.
|
||||
|
||||
|
@ -6394,7 +6394,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:72] is retrieved (see [[*Resolving idle time]]) and you are
|
||||
clock[fn:73] is retrieved (see [[*Resolving idle time]]) and you are
|
||||
prompted about what to do with it.
|
||||
|
||||
*** Clocking commands
|
||||
|
@ -6432,14 +6432,14 @@ prompted about what to do with it.
|
|||
the mode line, along with the title of the task. The clock 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:73]. If the
|
||||
line displays the current clocking time against it[fn:74]. If the
|
||||
task is a repeating one (see [[*Repeated tasks]]), show only the time
|
||||
since the last reset of the task[fn:74]. You can exercise more
|
||||
since the last reset of the task[fn:75]. 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:75]. Clicking with
|
||||
time, or ~auto~ which is the default[fn:76]. Clicking with
|
||||
{{{kbd(mouse-1)}}} onto the mode line entry pops up a menu with
|
||||
clocking options.
|
||||
|
||||
|
@ -6453,7 +6453,7 @@ prompted about what to do with it.
|
|||
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:76].
|
||||
timestamp[fn:77].
|
||||
|
||||
- {{{kbd(C-c C-x C-x)}}} (~org-clock-in-last~) ::
|
||||
|
||||
|
@ -6642,7 +6642,7 @@ be selected:
|
|||
| =thisweek=, =lastweek=, =thisweek-N= | a relative week |
|
||||
| =thismonth=, =lastmonth=, =thismonth-N= | a relative month |
|
||||
| =thisyear=, =lastyear=, =thisyear-N= | a relative year |
|
||||
| =untilnow=[fn:77] | all clocked time ever |
|
||||
| =untilnow=[fn:78] | all clocked time ever |
|
||||
|
||||
#+vindex: org-clock-display-default-range
|
||||
When this option is not set, Org falls back to the value in
|
||||
|
@ -6704,7 +6704,7 @@ using the =:formatter= parameter.
|
|||
|
||||
- =:lang= ::
|
||||
|
||||
Language[fn:78] to use for descriptive cells like "Task".
|
||||
Language[fn:79] to use for descriptive cells like "Task".
|
||||
|
||||
- =:link= ::
|
||||
|
||||
|
@ -6784,7 +6784,7 @@ day, you could write:
|
|||
#+end_example
|
||||
|
||||
#+texinfo: @noindent
|
||||
To use a specific time range you could write[fn:79]
|
||||
To use a specific time range you could write[fn:80]
|
||||
|
||||
#+begin_example
|
||||
,#+BEGIN: clocktable :tstart "<2006-08-10 Thu 10:00>"
|
||||
|
@ -6840,7 +6840,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:80], and ask what
|
||||
computer after being idle for that many minutes[fn:81], 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
|
||||
|
@ -7009,7 +7009,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:81], and
|
||||
column summarizes the estimated work effort for each day[fn:82], 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
|
||||
|
@ -7148,7 +7148,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:82] is set, a timestamp or a note is
|
||||
variable ~org-log-refile~[fn:83] is set, a timestamp or a note is
|
||||
recorded whenever an entry is refiled.
|
||||
|
||||
- {{{kbd(C-u C-c C-w)}}} ::
|
||||
|
@ -7620,7 +7620,7 @@ Now lets look at the elements of a template definition. Each entry in
|
|||
|
||||
- =(file+olp+datetree "filename" [ "Level 1 heading" ...])= ::
|
||||
|
||||
This target[fn:83] creates a heading in a date tree[fn:84] for
|
||||
This target[fn:84] creates a heading in a date tree[fn:85] 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
|
||||
|
@ -7645,7 +7645,7 @@ Now lets look at the elements of a template definition. Each entry in
|
|||
empty, an appropriate default template will be used. Otherwise this
|
||||
is a string with escape codes, which will be replaced depending on
|
||||
time and context of the capture call. You may also get this
|
||||
template string from a file[fn:85], or dynamically, from a function
|
||||
template string from a file[fn:86], or dynamically, from a function
|
||||
using either syntax:
|
||||
|
||||
: (file "/path/to/template-file")
|
||||
|
@ -7746,7 +7746,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:86] allow dynamic
|
||||
In the template itself, special "%-escapes"[fn:87] allow dynamic
|
||||
insertion of content. The templates are expanded in the order given
|
||||
here:
|
||||
|
||||
|
@ -7873,7 +7873,7 @@ here:
|
|||
After completing the template, position point here.
|
||||
|
||||
#+vindex: org-store-link-props
|
||||
For specific link types, the following keywords are defined[fn:87]:
|
||||
For specific link types, the following keywords are defined[fn:88]:
|
||||
|
||||
#+vindex: org-link-from-user-regexp
|
||||
| Link type | Available keywords |
|
||||
|
@ -7886,7 +7886,7 @@ For specific link types, the following keywords are defined[fn:87]:
|
|||
| | =%: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:88] |
|
||||
| | =%:fromto= (either "to NAME" or "from NAME")[fn:89] |
|
||||
| gnus | =%:group=, for messages also all email fields |
|
||||
| w3, w3m | =%:url= |
|
||||
| info | =%:file=, =%:node= |
|
||||
|
@ -17352,7 +17352,7 @@ they are mutually exclusive.
|
|||
|
||||
- =value= ::
|
||||
|
||||
Default for most Babel libraries[fn:142]. Functional mode. Org
|
||||
Default for most Babel libraries[fn:141]. 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
|
||||
|
@ -17926,10 +17926,10 @@ Code blocks in the following languages are supported.
|
|||
| Asymptote | =asymptote= | Lisp | =lisp= |
|
||||
| Awk | =awk= | Lua | =lua= |
|
||||
| C | =C= | MATLAB | =matlab= |
|
||||
| C++ | =C++=[fn:143] | Mscgen | =mscgen= |
|
||||
| C++ | =C++=[fn:142] | Mscgen | =mscgen= |
|
||||
| Clojure | =clojure= | Objective Caml | =ocaml= |
|
||||
| CSS | =css= | Octave | =octave= |
|
||||
| D | =D=[fn:144] | Org mode | =org= |
|
||||
| D | =D=[fn:143] | Org mode | =org= |
|
||||
| ditaa | =ditaa= | Oz | =oz= |
|
||||
| Emacs Calc | =calc= | Perl | =perl= |
|
||||
| Emacs Lisp | =emacs-lisp= | Plantuml | =plantuml= |
|
||||
|
@ -18060,7 +18060,7 @@ for Python and Emacs Lisp languages.
|
|||
|
||||
#+cindex: @samp{noweb-ref}, header argument
|
||||
Source code blocks can include references to other source code blocks,
|
||||
using a noweb[fn:145] style syntax:
|
||||
using a noweb[fn:144] style syntax:
|
||||
|
||||
: <<CODE-BLOCK-ID>>
|
||||
|
||||
|
@ -18571,7 +18571,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:146].
|
||||
init file[fn:145].
|
||||
|
||||
#+attr_texinfo: :columns 0.1 0.9
|
||||
| {{{kbd(a)}}} | =#+BEGIN_EXPORT ascii= ... =#+END_EXPORT= |
|
||||
|
@ -18651,7 +18651,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:147].
|
||||
the headline text[fn:146].
|
||||
|
||||
#+vindex: org-indent-indentation-per-level
|
||||
To make more horizontal space, the headlines are shifted by two
|
||||
|
@ -18679,9 +18679,9 @@ 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:148]. With Org's support, you have to indent all lines to
|
||||
Emacs[fn:147]. With Org's support, you have to indent all lines to
|
||||
line up with the outline headers. You would use these
|
||||
settings[fn:149]:
|
||||
settings[fn:148]:
|
||||
|
||||
#+begin_src emacs-lisp
|
||||
(setq org-adapt-indentation t
|
||||
|
@ -18948,7 +18948,7 @@ changes.
|
|||
|
||||
#+vindex: org-startup-indented
|
||||
Dynamic virtual indentation is controlled by the variable
|
||||
~org-startup-indented~[fn:150].
|
||||
~org-startup-indented~[fn:149].
|
||||
|
||||
| =indent= | Start with Org Indent mode turned on. |
|
||||
| =noindent= | Start with Org Indent mode turned off. |
|
||||
|
@ -19767,7 +19767,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:151] to interact with Emacs. Pass its location through
|
||||
a server[fn:150] 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:
|
||||
|
||||
|
@ -19788,7 +19788,7 @@ With a public server, consider encrypting the files. Org also
|
|||
requires OpenSSL installed on the local computer. To turn on
|
||||
encryption, set the same password in the mobile application and in
|
||||
Emacs. Set the password in the variable
|
||||
~org-mobile-use-encryption~[fn:152]. Note that even after the mobile
|
||||
~org-mobile-use-encryption~[fn:151]. Note that even after the mobile
|
||||
application encrypts the file contents, the file name remains visible
|
||||
on the file systems of the local computer, the server, and the mobile
|
||||
device.
|
||||
|
@ -19804,15 +19804,15 @@ The command ~org-mobile-push~ copies files listed in
|
|||
~org-mobile-files~ into the staging area. 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:153].
|
||||
~org-directory~, so all files should be inside this directory[fn:152].
|
||||
|
||||
Push creates a special Org file =agendas.org= with custom agenda views
|
||||
defined by the user[fn:154].
|
||||
defined by the user[fn:153].
|
||||
|
||||
Finally, Org writes the file =index.org=, containing links to other
|
||||
files. The mobile application reads this file first from the server
|
||||
to determine what other files to download for agendas. For faster
|
||||
downloads, it is expected to only read files whose checksums[fn:155]
|
||||
downloads, it is expected to only read files whose checksums[fn:154]
|
||||
have changed.
|
||||
|
||||
*** Pulling from the mobile application
|
||||
|
@ -19829,7 +19829,7 @@ data in an inbox file format, through the following steps:
|
|||
|
||||
1.
|
||||
#+vindex: org-mobile-inbox-for-pull
|
||||
Org moves all entries found in =mobileorg.org=[fn:156] and appends
|
||||
Org moves all entries found in =mobileorg.org=[fn:155] and appends
|
||||
them to the file pointed to by the variable
|
||||
~org-mobile-inbox-for-pull~. It should reside neither in the
|
||||
staging area nor on the server. Each captured entry and each
|
||||
|
@ -20125,9 +20125,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:157]. To activate it, put
|
||||
provided by =comment.sty=[fn:156]. To activate it, put
|
||||
~\usepackage{comment}~ in the document header. Orgtbl mode inserts
|
||||
a radio table skeleton[fn:158] with the command {{{kbd(M-x
|
||||
a radio table skeleton[fn:157] 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:
|
||||
|
||||
|
@ -20146,7 +20146,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:159]:
|
||||
features[fn:158]:
|
||||
|
||||
#+begin_example
|
||||
% BEGIN RECEIVE ORGTBL salesfigures
|
||||
|
@ -20362,7 +20362,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:160], ~todo~, ~alltodo~, ~tags~, ~tags-todo~,
|
||||
~agenda~, ~agenda*~[fn:159], ~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.
|
||||
|
@ -20405,7 +20405,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:161]. Then to selectively pick
|
||||
include all levels, use =LEVEL>0=[fn:160]. 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:
|
||||
|
@ -21524,63 +21524,68 @@ shift the date to tomorrow.
|
|||
[fn:62] 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:63] 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: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
|
||||
as 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] Org does not repeat inactive timestamps, however. See
|
||||
[fn:69] Org does not repeat inactive timestamps, however. See
|
||||
[[*Timestamps]].
|
||||
|
||||
[fn:69] In fact, the target state is taken from, in this sequence, the
|
||||
[fn:70] 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:70] You can change this using the option ~org-log-repeat~, or the
|
||||
[fn:71] 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:71] Clocking only works if all headings are indented with less
|
||||
[fn:72] 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:72] To resume the clock under the assumption that you have worked
|
||||
[fn:73] To resume the clock under the assumption that you have worked
|
||||
on this task while outside Emacs, use =(setq org-clock-persist t)=.
|
||||
|
||||
[fn:73] To add an effort estimate "on the fly", hook a function doing
|
||||
[fn:74] To add an effort estimate "on the fly", hook a function doing
|
||||
this to ~org-clock-in-prepare-hook~.
|
||||
|
||||
[fn:74] The last reset of the task is recorded by the =LAST_REPEAT=
|
||||
[fn:75] The last reset of the task is recorded by the =LAST_REPEAT=
|
||||
property.
|
||||
|
||||
[fn:75] See also the variable ~org-clock-mode-line-total~.
|
||||
[fn:76] See also the variable ~org-clock-mode-line-total~.
|
||||
|
||||
[fn:76] The corresponding in-buffer setting is: =#+STARTUP:
|
||||
[fn:77] The corresponding in-buffer setting is: =#+STARTUP:
|
||||
lognoteclock-out=.
|
||||
|
||||
[fn:77] When using ~:step~, ~untilnow~ starts from the beginning of
|
||||
[fn:78] When using ~:step~, ~untilnow~ starts from the beginning of
|
||||
2003, not the beginning of time.
|
||||
|
||||
[fn:78] Language terms can be set through the variable
|
||||
[fn:79] Language terms can be set through the variable
|
||||
~org-clock-clocktable-language-setup~.
|
||||
|
||||
[fn:79] Note that all parameters must be specified in a single
|
||||
[fn:80] Note that all parameters must be specified in a single
|
||||
line---the line is broken here only to fit it into the manual.
|
||||
|
||||
[fn:80] On computers using macOS, idleness is based on actual user
|
||||
[fn:81] 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
|
||||
|
@ -21588,39 +21593,35 @@ 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:81] Please note the pitfalls of summing hierarchical data in
|
||||
[fn:82] Please note the pitfalls of summing hierarchical data in
|
||||
a flat list (see [[*Using Column View in the Agenda]]).
|
||||
|
||||
[fn:82] Note the corresponding =STARTUP= options =logrefile=,
|
||||
[fn:83] Note the corresponding =STARTUP= options =logrefile=,
|
||||
=lognoterefile=, and =nologrefile=.
|
||||
|
||||
[fn:83] Org used to offer four different targets for date/week tree
|
||||
[fn:84] 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:84] A date tree is an outline structure with years on the highest
|
||||
[fn:85] 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:85] When the file name is not absolute, Org assumes it is relative
|
||||
[fn:86] When the file name is not absolute, Org assumes it is relative
|
||||
to ~org-directory~.
|
||||
|
||||
[fn:86] If you need one of these sequences literally, escape the =%=
|
||||
[fn:87] If you need one of these sequences literally, escape the =%=
|
||||
with a backslash.
|
||||
|
||||
[fn:87] If you define your own link types (see [[*Adding Hyperlink
|
||||
[fn:88] 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:88] This is always the other, not the user. See the variable
|
||||
[fn:89] This is always the other, not the user. See the variable
|
||||
~org-link-from-user-regexp~.
|
||||
|
||||
[fn:89] If you move entries or Org files from one directory to
|
||||
another, you may want to configure ~org-attach-id-dir~ to contain
|
||||
an absolute path.
|
||||
|
||||
[fn:90] 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.
|
||||
|
@ -21746,9 +21747,7 @@ and =#+STARTUP: nofnadjust=.
|
|||
[fn:121] The variable ~org-export-date-timestamp-format~ defines how
|
||||
this timestamp are exported.
|
||||
|
||||
[fn:122] 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:122] DEFINITION NOT FOUND.
|
||||
|
||||
[fn:123] At the moment, some export back-ends do not obey this
|
||||
specification. For example, LaTeX export excludes every unnumbered
|
||||
|
@ -21817,68 +21816,64 @@ to remove code evaluation from the {{{kbd(C-c C-c)}}} key binding.
|
|||
are not evaluated when they appear in a keyword (see [[*Summary of
|
||||
In-Buffer Settings]]).
|
||||
|
||||
[fn:142] For shell source blocks, the default is to return the output.
|
||||
If you want to enforce returning the exit status, add =:results value=
|
||||
explicitly.
|
||||
|
||||
[fn:143] C++ language is handled in =ob-C.el=. Even though the
|
||||
[fn:142] C++ language is handled in =ob-C.el=. Even though the
|
||||
identifier for such source blocks is =C++=, you activate it by loading
|
||||
the C language.
|
||||
|
||||
[fn:144] D language is handled in =ob-C.el=. Even though the
|
||||
[fn:143] D language is handled in =ob-C.el=. Even though the
|
||||
identifier for such source blocks is =D=, you activate it by loading
|
||||
the C language.
|
||||
|
||||
[fn:145] For noweb literate programming details, see
|
||||
[fn:144] For noweb literate programming details, see
|
||||
http://www.cs.tufts.edu/~nr/noweb/.
|
||||
|
||||
[fn:146] For more information, please refer to the commentary section
|
||||
[fn:145] For more information, please refer to the commentary section
|
||||
in =org-tempo.el=.
|
||||
|
||||
[fn:147] Org Indent mode also sets ~wrap-prefix~ correctly for
|
||||
[fn:146] 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:148] This works, but requires extra effort. Org Indent mode is
|
||||
[fn:147] This works, but requires extra effort. Org Indent mode is
|
||||
more convenient for most applications.
|
||||
|
||||
[fn:149] ~org-adapt-indentation~ can also be set to ='headline-data=,
|
||||
[fn:148] ~org-adapt-indentation~ can also be set to ='headline-data=,
|
||||
in which case only data lines below the headline will be indented.
|
||||
|
||||
[fn:150] Note that Org Indent mode also sets the ~wrap-prefix~
|
||||
[fn:149] 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:151] For a server to host files, consider using a WebDAV server,
|
||||
[fn:150] 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:152] If Emacs is configured for safe storing of passwords, then
|
||||
[fn:151] 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:153] Symbolic links in ~org-directory~ need to have the same name
|
||||
[fn:152] Symbolic links in ~org-directory~ need to have the same name
|
||||
as their targets.
|
||||
|
||||
[fn:154] While creating the agendas, Org mode forces =ID= properties
|
||||
[fn:153] 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:155] Checksums are stored automatically in the file
|
||||
[fn:154] Checksums are stored automatically in the file
|
||||
=checksums.dat=.
|
||||
|
||||
[fn:156] The file will be empty after this operation.
|
||||
[fn:155] The file will be empty after this operation.
|
||||
|
||||
[fn:157] https://www.ctan.org/pkg/comment
|
||||
[fn:156] https://www.ctan.org/pkg/comment
|
||||
|
||||
[fn:158] By default this works only for LaTeX, HTML, and Texinfo.
|
||||
[fn:157] By default this works only for LaTeX, HTML, and Texinfo.
|
||||
Configure the variable ~orgtbl-radio-table-templates~ to install
|
||||
templates for other modes.
|
||||
|
||||
[fn:159] If the =TBLFM= keyword contains an odd number of dollar
|
||||
[fn:158] 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
|
||||
|
@ -21886,9 +21881,13 @@ 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:160] The ~agenda*~ view is the same as ~agenda~ except that it
|
||||
[fn:159] 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:161] Note that, for ~org-odd-levels-only~, a level number
|
||||
[fn:160] Note that, for ~org-odd-levels-only~, a level number
|
||||
corresponds to order in the hierarchy, not to the number of stars.
|
||||
|
||||
[fn:161] If you move entries or Org files from one directory to
|
||||
another, you may want to configure ~org-attach-id-dir~ to contain
|
||||
an absolute path.
|
||||
|
|
Loading…
Reference in New Issue