daniel/emacs-conf
1
2
Fork 0
Code Issues 7 Pull Requests Projects Releases Wiki Activity

update of packages

Browse Source
This commit is contained in:
Daniel Weschke
2023-11-04 19:26:41 +01:00
parent e162a12b58
commit 3b54a3236d
726 changed files with 297673 additions and 34585 deletions
Download Patch File Download Diff File Expand all files Collapse all files
lisp/org/doc/doc-setup.org
+1 -1
View File
@@ -1,6 +1,6 @@
# SETUPFILE for Org manual
# Copyright (C) 2021-2022 Free Software Foundation, Inc.
# Copyright (C) 2021-2023 Free Software Foundation, Inc.
#
# This file is part of GNU Emacs.
#
lisp/org/doc/org-guide.org
+8 -8
View File
@@ -10,7 +10,7 @@
:copying: t
:END:
Copyright \copy 2004--2022 Free Software Foundation, Inc.
Copyright \copy 2004--2023 Free Software Foundation, Inc.
#+begin_quote
Permission is granted to copy, distribute and/or modify this document
@@ -141,7 +141,7 @@ See [[*Miscellaneous]] for a setup to realize this.
Outlines make it possible to hide parts of the text in the buffer.
Org uses just two commands, bound to {{{kbd(TAB)}}} and
{{{kbd{S-TAB)}}} to change the visibility in the buffer.
{{{kbd(S-TAB)}}} to change the visibility in the buffer.
#+attr_texinfo: :sep ,
- {{{kbd(TAB)}}} ::
@@ -667,7 +667,7 @@ of the option ~org-todo-state-tags-triggers~ for details.
:DESCRIPTION: More than just on/off.
:END:
You can use TODO keywords to indicate @emph{sequential} working progress
You can use TODO keywords to indicate /sequential/ working progress
states:
#+begin_src emacs-lisp
@@ -1093,7 +1093,7 @@ 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>=.
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 [[*The Weekly/daily Agenda]]). We distinguish:
the agenda (see [[*The Weekly/Daily Agenda]]). We distinguish:
- Plain timestamp; Event; Appointment ::
@@ -1111,8 +1111,8 @@ the agenda (see [[*The Weekly/daily Agenda]]). We distinguish:
A timestamp may contain a /repeater interval/, indicating that it
applies not only on the given date, but again and again after
a certain interval of N days (d), weeks (w), months (m), or years
(y). The following shows up in the agenda every Wednesday:
a certain interval of N hours (h), days (d), weeks (w), months (m),
or years (y). The following shows up in the agenda every Wednesday:
#+begin_example
,* Pick up Sam at school
@@ -1294,7 +1294,7 @@ a project.
a {{{kbd(C-u)}}} prefix argument, select the target task from a list
of recently clocked tasks.
The {{{kbd(l)}}} key may be used in the agenda (see [[*The Weekly/daily
The {{{kbd(l)}}} key may be used in the agenda (see [[*The Weekly/Daily
Agenda]]) to show which tasks have been worked on or closed during
a day.
@@ -1527,7 +1527,7 @@ commands:
#+attr_texinfo: :sep ,
- {{{kbd(a)}}} ::
Create the calendar-like agenda (see [[*The Weekly/daily Agenda]]).
Create the calendar-like agenda (see [[*The Weekly/Daily Agenda]]).
- {{{kbd(t)}}}, {{{kbd(T)}}} ::
lisp/org/doc/org-manual.org
+49 -34
View File
@@ -1249,11 +1249,12 @@ After the drawer.
#+findex: org-insert-drawer
You can interactively insert a drawer at point by calling
~org-insert-drawer~, which is bound to {{{kbd(C-c C-x d)}}}. With an
active region, this command puts the region inside the drawer. With
a prefix argument, this command calls ~org-insert-property-drawer~,
which creates a =PROPERTIES= drawer right below the current headline.
Org mode uses this special drawer for storing properties (see
[[*Properties and Columns]]). You cannot use it for anything else.
active region, this command puts the region inside the drawer. With a
prefix argument, this command calls non-interactive function
~org-insert-property-drawer~, which creates a =PROPERTIES= drawer
right below the current headline. Org mode uses this special drawer
for storing properties (see [[*Properties and Columns]]). You cannot use
it for anything else.
Completion over drawer keywords is also possible using
{{{kbd(M-TAB)}}}[fn:6].
@@ -1401,7 +1402,7 @@ you, configure the option ~org-table-auto-blank-field~.
- {{{kbd(M-x org-table-blank-field)}}} ::
#+findex: org-table-blank-field
Blank the field at point.
Blank the current table field or active region.
- {{{kbd(S-TAB)}}} (~org-table-previous-field~) ::
@@ -4561,7 +4562,7 @@ all children are done, you can use the following setup:
#+begin_src emacs-lisp
(defun org-summary-todo (n-done n-not-done)
"Switch entry to DONE when all subentries are done, to TODO otherwise."
(let (org-log-done org-log-states) ; turn off logging
(let (org-log-done org-todo-log-states) ; turn off logging
(org-todo (if (= n-not-done 0) "DONE" "TODO"))))
(add-hook 'org-after-todo-statistics-hook #'org-summary-todo)
@@ -5290,7 +5291,7 @@ The following commands help to work with properties:
Set a property in the current entry. Both the property and the
value can be inserted using completion.
- {{{kbd(S-RIGHT)}}} (~org-property-next-allowed-values~), {{{kbd(S-LEFT)}}} (~org-property-previous-allowed-value~) ::
- {{{kbd(S-RIGHT)}}} (~org-property-next-allowed-value~), {{{kbd(S-LEFT)}}} (~org-property-previous-allowed-value~) ::
#+kindex: S-RIGHT
#+kindex: S-LEFT
@@ -5957,8 +5958,9 @@ the agenda (see [[*Weekly/daily agenda]]). We distinguish:
#+findex: org-block
For more complex date specifications, Org mode supports using the
special expression diary entries implemented in the Emacs Calendar
package[fn:20]. For example, with optional time:
special expression diary entries implemented in the
[[info:emacs#Special Diary Entries][Emacs Calendar package]][fn:20].
For example, with optional time:
#+begin_example
,* 22:00-23:00 The nerd meeting on every 2nd Thursday of the month
@@ -8787,7 +8789,9 @@ a ~day~, ~week~, ~month~ or ~year~. For weekly agendas, the default
is to start on the previous Monday (see
~org-agenda-start-on-weekday~). You can also set the start date using
a date shift: =(setq org-agenda-start-day "+10d")= starts the agenda
ten days from today in the future.
ten days from today in the future. ~org-agenda-start-on-weekday~
takes precedence over ~org-agenda-start-day~ in weekly and bi-weekly
agendas.
Remote editing from the agenda buffer means, for example, that you can
change the dates of deadlines and appointments from the agenda buffer.
@@ -10249,9 +10253,9 @@ the other commands, point needs to be in the desired line.
Unmark entry for bulk action.
- {{{kbd(U)}}} (~org-agenda-bulk-remove-all-marks~) ::
- {{{kbd(U)}}} (~org-agenda-bulk-unmark-all~) ::
#+kindex: U
#+findex: org-agenda-bulk-remove-all-marks
#+findex: org-agenda-bulk-unmark-all
Unmark all marked entries for bulk action.
@@ -11689,9 +11693,9 @@ When the variable ~org-export-dispatch-use-expert-ui~ is set to
a non-~nil~ value, Org prompts in the minibuffer. To switch back to
the hierarchical menu, press {{{kbd(?)}}}.
- {{{kbd(C-c C-e)}}} (~org-export~) ::
- {{{kbd(C-c C-e)}}} (~org-export-dispatch~) ::
#+kindex: C-c C-e
#+findex: org-export
#+findex: org-export-dispatch
Invokes the export dispatcher interface. The options show default
settings. The {{{kbd(C-u)}}} prefix argument preserves options from
@@ -12229,7 +12233,7 @@ with the custom ID =theory=, you can use
The following command allows navigating to the included document:
- {{{kbd(C-c ')}}} (~org-edit~special~) ::
- {{{kbd(C-c ')}}} (~org-edit-special~) ::
#+kindex: C-c '
#+findex: org-edit-special
@@ -13722,7 +13726,7 @@ A sample Org file with the above headers:
#+vindex: org-export-default-language
LaTeX packages =babel= or =polyglossia= can also be loaded in a
document. The "AUTO" string will be replaced in both cases by the
appropiate value for the =LANGUAGE= keyword, if present in the
appropriate value for the =LANGUAGE= keyword, if present in the
document, or by the value of ~org-export-default-language~. Let's see
some examples in one or another case.
@@ -14360,10 +14364,10 @@ executable. Without it, export cannot finish.
:DESCRIPTION: Invoking export.
:END:
- {{{kbd(C-c C-e o o)}}} (~org-export-to-odt~) ::
- {{{kbd(C-c C-e o o)}}} (~org-odt-export-to-odt~) ::
#+kindex: C-c C-e o o
#+findex: org-export-to-odt
#+findex: org-odt-export-to-odt
Export as OpenDocument Text file.
#+cindex: @samp{EXPORT_FILE_NAME}, property
@@ -16030,7 +16034,12 @@ can remove every headline in the buffer during export like this:
"Remove all headlines in the current buffer.
BACKEND is the export back-end being used, as a symbol."
(org-map-entries
(lambda () (delete-region (point) (line-beginning-position 2)))))
(lambda ()
(delete-region (point) (line-beginning-position 2))
;; We need to tell `org-map-entries' to not skip over heading at
;; point. Otherwise, it would continue from _next_ heading. See
;; the docstring of `org-map-entries' for details.
(setq org-map-continue-from (point)))))
(add-hook 'org-export-before-parsing-hook #'my-headline-removal)
#+end_src
@@ -18093,7 +18102,8 @@ evaluating untrusted code blocks by prompting for a confirmation.
- =yes= ::
Org always evaluates the source code without asking permission.
Org evaluates the source code, possibly asking permission according
to ~org-confirm-babel-evaluate~.
- =never= or =no= ::
@@ -18491,7 +18501,7 @@ options; they are mutually exclusive.
Ignore the results completely. This option is similar to =none=,
but no processing is performed on the return value. Calling the
code block programatically (see [[*How to evaluate source code]]) or by
code block programmatically (see [[*How to evaluate source code]]) or by
reference (see [[*Passing arguments]] and [[*Noweb Reference Syntax]]) will
always yield nil.
@@ -18784,7 +18794,7 @@ a octal shorthand is defined, =oXXX= (=o= for octal). Using this, our
read-only example is =:tangle-mode o444=. Omitting the =o= prefix will
cause the argument to be interpreted as an integer, which can lead to
unexpected results (=444= is the same as =o674=).
Two other shorthands are recognised, ls-style strings like
Two other shorthands are recognized, ls-style strings like
=rw-r--r--=, and chmod-style permissions like =g+w=.
Note that chmod-style permissions are based on
~org-babel-tangle-default-file-mode~, which is =#o544= by default.
@@ -18792,7 +18802,7 @@ Note that chmod-style permissions are based on
When =:tangle-mode= and =:shebang= are both specified, the give
=:tangle-mode= will override the permissions from =:shebang=. When
multiple source code blocks tangle to a single file with conflicting
=:tangle-mode= header arguments, Org's behaviour is undefined.
=:tangle-mode= header arguments, Org's behavior is undefined.
#+cindex: @samp{no-expand}, header argument
By default Org expands code blocks during tangling. The =no-expand=
@@ -20021,11 +20031,16 @@ changes.
| =nofnadjust= | Do not renumber and sort automatically. |
#+vindex: org-hide-block-startup
To hide blocks on startup, use these keywords. The
corresponding variable is ~org-hide-block-startup~.
#+vindex: org-hide-drawer-startup
To hide blocks or drawers on startup, use these keywords. The
corresponding variables are ~org-hide-block-startup~ and
~org-hide-drawer-startup~.
| =hideblocks= | Hide all begin/end blocks on startup. |
| =nohideblocks= | Do not hide blocks on startup. |
| =hidedrawers= | Hide all begin/end blocks on startup. |
| =nohidedrawers= | Do not hide blocks on startup. |
| =hideblocks= | Hide all begin/end blocks on startup. |
| =nohideblocks= | Do not hide blocks on startup. |
#+vindex: org-pretty-entities
The display of entities as UTF-8 characters is governed by the
@@ -20251,12 +20266,12 @@ packages are documented here.
#+vindex: org-table-formula-constants
Org can use names for constants in formulas in tables. Org can also
use calculation suffixes for units, such as =M= for =Mega=. For
a standard collection of such constants, install the =constants=
use calculation suffixes for units, such as =M= for =Mega=. For a
standard collection of such constants, install the =constants=
package. Install version 2.0 of this package, available at
[[http://www.astro.uva.nl/~dominik/Tools]]. Org checks if the function
~constants-get~ has been autoloaded. Installation instructions are
in the file =constants.el=.
[[https://github.com/cdominik/constants-for-Emacs]]. Org checks if the
function ~constants-get~ has been autoloaded. Installation
instructions are in the file =constants.el=.
- =cdlatex.el= by Carsten Dominik ::
#+cindex: @file{cdlatex.el}
@@ -22300,7 +22315,7 @@ that are mentioned in the manual. For a more complete list, use
This manual is for Org version {{{version}}}.
Copyright \copy 2004--2022 Free Software Foundation, Inc.
Copyright \copy 2004--2023 Free Software Foundation, Inc.
#+begin_quote
Permission is granted to copy, distribute and/or modify this document
lisp/org/doc/org-version.inc
+2 -2
View File
@@ -1,3 +1,3 @@
@c automatically generated, do not edit
@set VERSION 9.6 ()
@set DATE 2022-12-17
@set VERSION 9.6.11 ()
@set DATE 2023-11-04
lisp/org/doc/org.texi
+56 -39
View File
@@ -15,7 +15,7 @@
@copying
This manual is for Org version 9.6.
Copyright @copyright{} 2004--2022 Free Software Foundation, Inc.
Copyright @copyright{} 2004--2023 Free Software Foundation, Inc.
@quotation
Permission is granted to copy, distribute and/or modify this document
@@ -1776,11 +1776,12 @@ After the drawer.
@findex org-insert-drawer
You can interactively insert a drawer at point by calling
@code{org-insert-drawer}, which is bound to @kbd{C-c C-x d}. With an
active region, this command puts the region inside the drawer. With
a prefix argument, this command calls @code{org-insert-property-drawer},
which creates a @samp{PROPERTIES} drawer right below the current headline.
Org mode uses this special drawer for storing properties (see
@ref{Properties and Columns}). You cannot use it for anything else.
active region, this command puts the region inside the drawer. With a
prefix argument, this command calls non-interactive function
@code{org-insert-property-drawer}, which creates a @samp{PROPERTIES} drawer
right below the current headline. Org mode uses this special drawer
for storing properties (see @ref{Properties and Columns}). You cannot use
it for anything else.
Completion over drawer keywords is also possible using
@kbd{M-@key{TAB}}@footnote{Many desktops intercept @kbd{M-@key{TAB}} to switch windows.
@@ -1929,7 +1930,7 @@ necessary.
@item @kbd{M-x org-table-blank-field}
@findex org-table-blank-field
Blank the field at point.
Blank the current table field or active region.
@item @kbd{S-@key{TAB}} (@code{org-table-previous-field})
@kindex S-TAB
@@ -5116,7 +5117,7 @@ all children are done, you can use the following setup:
@lisp
(defun org-summary-todo (n-done n-not-done)
"Switch entry to DONE when all subentries are done, to TODO otherwise."
(let (org-log-done org-log-states) ; turn off logging
(let (org-log-done org-todo-log-states) ; turn off logging
(org-todo (if (= n-not-done 0) "DONE" "TODO"))))
(add-hook 'org-after-todo-statistics-hook #'org-summary-todo)
@@ -5882,7 +5883,7 @@ With point in a property drawer, this executes property commands.
Set a property in the current entry. Both the property and the
value can be inserted using completion.
@item @kbd{S-@key{RIGHT}} (@code{org-property-next-allowed-values})
@item @kbd{S-@key{RIGHT}} (@code{org-property-next-allowed-value})
@itemx @kbd{S-@key{LEFT}} (@code{org-property-previous-allowed-value})
@kindex S-RIGHT
@kindex S-LEFT
@@ -6573,8 +6574,8 @@ or years (y). The following shows up in the agenda every Wednesday:
@findex org-block
For more complex date specifications, Org mode supports using the
special expression diary entries implemented in the Emacs Calendar
package@footnote{When working with the standard diary expression functions, you
special expression diary entries implemented in the
@ref{Special Diary Entries,Emacs Calendar package,,emacs,}@footnote{When working with the standard diary expression functions, you
need to be very careful with the order of the arguments. That order
depends evilly on the variable @code{calendar-date-style}. For example, to
specify a date December 1, 2005, the call might look like
@@ -6585,7 +6586,8 @@ these functions, namely @code{org-date}, @code{org-anniversary}, @code{org-cycli
~org-block}. These work just like the corresponding @code{diary-}
functions, but with stable ISO order of arguments (year, month, day)
wherever applicable, independent of the value of
@code{calendar-date-style}.}. For example, with optional time:
@code{calendar-date-style}.}.
For example, with optional time:
@example
* 22:00-23:00 The nerd meeting on every 2nd Thursday of the month
@@ -9435,7 +9437,9 @@ a @code{day}, @code{week}, @code{month} or @code{year}. For weekly agendas, the
is to start on the previous Monday (see
@code{org-agenda-start-on-weekday}). You can also set the start date using
a date shift: @samp{(setq org-agenda-start-day "+10d")} starts the agenda
ten days from today in the future.
ten days from today in the future. @code{org-agenda-start-on-weekday}
takes precedence over @code{org-agenda-start-day} in weekly and bi-weekly
agendas.
Remote editing from the agenda buffer means, for example, that you can
change the dates of deadlines and appointments from the agenda buffer.
@@ -10848,9 +10852,9 @@ Mark all visible agenda entries for bulk action.
Unmark entry for bulk action.
@item @kbd{U} (@code{org-agenda-bulk-remove-all-marks})
@item @kbd{U} (@code{org-agenda-bulk-unmark-all})
@kindex U
@findex org-agenda-bulk-remove-all-marks
@findex org-agenda-bulk-unmark-all
Unmark all marked entries for bulk action.
@@ -12359,9 +12363,9 @@ a non-@code{nil} value, Org prompts in the minibuffer. To switch back to
the hierarchical menu, press @kbd{?}.
@table @asis
@item @kbd{C-c C-e} (@code{org-export})
@item @kbd{C-c C-e} (@code{org-export-dispatch})
@kindex C-c C-e
@findex org-export
@findex org-export-dispatch
Invokes the export dispatcher interface. The options show default
settings. The @kbd{C-u} prefix argument preserves options from
@@ -12886,7 +12890,7 @@ with the custom ID @samp{theory}, you can use
The following command allows navigating to the included document:
@table @asis
@item @kbd{C-c '} (@code{org-edit~special})
@item @kbd{C-c '} (@code{org-edit-special})
@kindex C-c '
@findex org-edit-special
@@ -14449,7 +14453,7 @@ A sample Org file with the above headers:
@vindex org-export-default-language
@LaTeX{} packages @samp{babel} or @samp{polyglossia} can also be loaded in a
document. The ``AUTO'' string will be replaced in both cases by the
appropiate value for the @samp{LANGUAGE} keyword, if present in the
appropriate value for the @samp{LANGUAGE} keyword, if present in the
document, or by the value of @code{org-export-default-language}. Let's see
some examples in one or another case.
@@ -15084,9 +15088,9 @@ executable. Without it, export cannot finish.
@subsection ODT export commands
@table @asis
@item @kbd{C-c C-e o o} (@code{org-export-to-odt})
@item @kbd{C-c C-e o o} (@code{org-odt-export-to-odt})
@kindex C-c C-e o o
@findex org-export-to-odt
@findex org-odt-export-to-odt
Export as OpenDocument Text file.
@cindex @samp{EXPORT_FILE_NAME}, property
@@ -16765,7 +16769,12 @@ can remove every headline in the buffer during export like this:
"Remove all headlines in the current buffer.
BACKEND is the export back-end being used, as a symbol."
(org-map-entries
(lambda () (delete-region (point) (line-beginning-position 2)))))
(lambda ()
(delete-region (point) (line-beginning-position 2))
;; We need to tell `org-map-entries' to not skip over heading at
;; point. Otherwise, it would continue from _next_ heading. See
;; the docstring of `org-map-entries' for details.
(setq org-map-continue-from (point)))))
(add-hook 'org-export-before-parsing-hook #'my-headline-removal)
@end lisp
@@ -16842,7 +16851,7 @@ is the type targeted by the filter. Valid types are:
@tab verse-block
@end multitable
Here is an example filter that replaces non-breaking spaces ~ ~ in the
Here is an example filter that replaces non-breaking spaces @code{ } in the
Org buffer with @samp{~} for the @LaTeX{} back-end.
@lisp
@@ -19106,7 +19115,8 @@ evaluating untrusted code blocks by prompting for a confirmation.
@table @asis
@item @samp{yes}
Org always evaluates the source code without asking permission.
Org evaluates the source code, possibly asking permission according
to @code{org-confirm-babel-evaluate}.
@item @samp{never} or @samp{no}
Org never evaluates the source code.
@@ -19475,7 +19485,7 @@ Usage example: @samp{:results none}.
@item @samp{discard}
Ignore the results completely. This option is similar to @samp{none},
but no processing is performed on the return value. Calling the
code block programatically (see @ref{How to evaluate source code}) or by
code block programmatically (see @ref{How to evaluate source code}) or by
reference (see @ref{Passing arguments} and @ref{Noweb Reference Syntax}) will
always yield nil.
@@ -19756,7 +19766,7 @@ a octal shorthand is defined, @samp{oXXX} (@samp{o} for octal). Using this, our
read-only example is @samp{:tangle-mode o444}. Omitting the @samp{o} prefix will
cause the argument to be interpreted as an integer, which can lead to
unexpected results (@samp{444} is the same as @samp{o674}).
Two other shorthands are recognised, ls-style strings like
Two other shorthands are recognized, ls-style strings like
@samp{rw-r--r--}, and chmod-style permissions like @samp{g+w}.
Note that chmod-style permissions are based on
@code{org-babel-tangle-default-file-mode}, which is @samp{#o544} by default.
@@ -19764,7 +19774,7 @@ Note that chmod-style permissions are based on
When @samp{:tangle-mode} and @samp{:shebang} are both specified, the give
@samp{:tangle-mode} will override the permissions from @samp{:shebang}. When
multiple source code blocks tangle to a single file with conflicting
@samp{:tangle-mode} header arguments, Org's behaviour is undefined.
@samp{:tangle-mode} header arguments, Org's behavior is undefined.
@cindex @samp{no-expand}, header argument
By default Org expands code blocks during tangling. The @samp{no-expand}
@@ -21136,15 +21146,23 @@ corresponding variables are @code{org-footnote-define-inline},
@end multitable
@vindex org-hide-block-startup
To hide blocks on startup, use these keywords. The
corresponding variable is @code{org-hide-block-startup}.
@vindex org-hide-drawer-startup
To hide blocks or drawers on startup, use these keywords. The
corresponding variables are @code{org-hide-block-startup} and
@code{org-hide-drawer-startup}.
@multitable {aaaaaaaaaaaaaa} {aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa}
@multitable {aaaaaaaaaaaaaaa} {aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa}
@item @samp{hideblocks}
@tab Hide all begin/end blocks on startup.
@item @samp{nohideblocks}
@tab Do not hide blocks on startup.
@item @samp{hidedrawers}
@tab Hide all begin/end blocks on startup.
@item @samp{nohidedrawers}
@tab Do not hide blocks on startup.
@end multitable
@end table
@vindex org-pretty-entities
The display of entities as UTF-8 characters is governed by the
@@ -21157,6 +21175,7 @@ variable @code{org-pretty-entities} and the keywords
@tab Leave entities plain.
@end multitable
@table @asis
@item @samp{#+TAGS: TAG1(c1) TAG2(c2)}
@cindex @samp{TAGS}, keyword
@vindex org-tag-alist
@@ -21164,9 +21183,7 @@ These lines (several such lines are allowed) specify the valid tags
in this file, and (potentially) the corresponding @emph{fast tag
selection} keys. The corresponding variable is @code{org-tag-alist}.
@item @samp{#+TODO:}
@itemx @samp{#+SEQ_TODO:}
@itemx @samp{#+TYP_TODO:}
@item @samp{#+TODO:}, @samp{#+SEQ_TODO:}, @samp{#+TYP_TODO:}
@cindex @samp{SEQ_TODO}, keyword
@cindex @samp{TODO}, keyword
@cindex @samp{TYP_TODO}, keyword
@@ -21380,12 +21397,12 @@ embedded calculations. See @ref{Embedded Mode,GNU Emacs Calc Manual,,calc,}.
@vindex org-table-formula-constants
Org can use names for constants in formulas in tables. Org can also
use calculation suffixes for units, such as @samp{M} for @samp{Mega}. For
a standard collection of such constants, install the @samp{constants}
use calculation suffixes for units, such as @samp{M} for @samp{Mega}. For a
standard collection of such constants, install the @samp{constants}
package. Install version 2.0 of this package, available at
@uref{http://www.astro.uva.nl/~dominik/Tools}. Org checks if the function
@code{constants-get} has been autoloaded. Installation instructions are
in the file @samp{constants.el}.
@uref{https://github.com/cdominik/constants-for-Emacs}. Org checks if the
function @code{constants-get} has been autoloaded. Installation
instructions are in the file @samp{constants.el}.
@item @samp{cdlatex.el} by Carsten Dominik
@cindex @file{cdlatex.el}
@@ -24106,4 +24123,4 @@ that are mentioned in the manual. For a more complete list, use
@printindex vr
@bye
@bye
lisp/org/doc/orgcard.tex
+2 -2
View File
@@ -15,7 +15,7 @@
\pdflayout=(0l)
% Nothing else needs to be changed below this line.
% Copyright (C) 1987, 1993, 1996--1997, 2001--2022 Free Software
% Copyright (C) 1987, 1993, 1996--1997, 2001--2023 Free Software
% Foundation, Inc.
% This document is free software: you can redistribute it and/or modify
@@ -324,7 +324,7 @@
\key{archive subtree using the default command}{C-c C-x C-a}
\key{move subtree to archive file}{C-c C-x C-s}
\key{toggle ARCHIVE tag / to ARCHIVE sibling}{C-c C-x a/A}
\key{force cycling of an ARCHIVEd tree}{C-TAB}
\key{force cycling of an ARCHIVEd tree}{C-c C-TAB}
\section{Filtering and Sparse Trees}
lisp/org/doc/orgguide.texi
+9 -9
View File
@@ -13,7 +13,7 @@
@c %**end of header
@copying
Copyright @copyright{} 2004--2022 Free Software Foundation, Inc.
Copyright @copyright{} 2004--2023 Free Software Foundation, Inc.
@quotation
Permission is granted to copy, distribute and/or modify this document
@@ -257,7 +257,7 @@ See @ref{Miscellaneous} for a setup to realize this.
Outlines make it possible to hide parts of the text in the buffer.
Org uses just two commands, bound to @kbd{@key{TAB}} and
@{@{@{kbd@{S-TAB)@}@}@} to change the visibility in the buffer.
@kbd{S-@key{TAB}} to change the visibility in the buffer.
@table @asis
@item @kbd{@key{TAB}}
@@ -795,7 +795,7 @@ of the option @code{org-todo-state-tags-triggers} for details.
@node Multi-state Workflow
@section Multi-state Workflow
You can use TODO keywords to indicate @@emph@{sequential@} working progress
You can use TODO keywords to indicate @emph{sequential} working progress
states:
@lisp
@@ -1220,7 +1220,7 @@ a range of times---in a special format, either @samp{<2003-09-16 Tue>} or
@samp{<2003-09-16 Tue 09:39>} or @samp{<2003-09-16 Tue 12:00-12:30>}.
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 [BROKEN LINK: *The Weekly/daily Agenda]). We distinguish:
the agenda (see @ref{Built-in Agenda Views}). We distinguish:
@table @asis
@item Plain timestamp; Event; Appointment
@@ -1237,8 +1237,8 @@ just like writing down an appointment or event in a paper agenda.
@item Timestamp with repeater interval
A timestamp may contain a @emph{repeater interval}, indicating that it
applies not only on the given date, but again and again after
a certain interval of N days (d), weeks (w), months (m), or years
(y). The following shows up in the agenda every Wednesday:
a certain interval of N hours (h), days (d), weeks (w), months (m),
or years (y). The following shows up in the agenda every Wednesday:
@example
* Pick up Sam at school
@@ -1411,7 +1411,7 @@ a @kbd{C-u} prefix argument, select the target task from a list
of recently clocked tasks.
@end table
The @kbd{l} key may be used in the agenda (see [BROKEN LINK: *The Weekly/daily Agenda]) to show which tasks have been worked on or closed during
The @kbd{l} key may be used in the agenda (see @ref{Built-in Agenda Views}) to show which tasks have been worked on or closed during
a day.
@node Capture Refile Archive
@@ -1646,7 +1646,7 @@ commands:
@table @asis
@item @kbd{a}
Create the calendar-like agenda (see [BROKEN LINK: *The Weekly/daily Agenda]).
Create the calendar-like agenda (see @ref{Built-in Agenda Views}).
@item @kbd{t}
@itemx @kbd{T}
@@ -2685,4 +2685,4 @@ support in a file, use
#+STARTUP: hidestars odd
@end example
@bye
@bye