commit | author | age
|
76bbd0
|
1 |
;ELC |
C |
2 |
;;; Compiled |
|
3 |
;;; in Emacs version 26.1 |
|
4 |
;;; with all optimizations. |
|
5 |
|
|
6 |
;;; This file contains utf-8 non-ASCII characters, |
|
7 |
;;; and so cannot be loaded into Emacs 22 or earlier. |
|
8 |
(and (boundp 'emacs-version) |
|
9 |
(< (aref emacs-version (1- (length emacs-version))) ?A) |
|
10 |
(string-lessp emacs-version "23") |
|
11 |
(error "`%s' was compiled for Emacs 23 or later" #$)) |
|
12 |
|
|
13 |
;;;;;;;;;;;;;;;;;;;;;;;;;;;;; |
|
14 |
|
|
15 |
|
|
16 |
(byte-code "\300\301!\210\300\302!\210\300\303!\207" [require cl-lib org org-macs] 2) |
|
17 |
(defvar org-agenda-buffer-name "*Org Agenda*") |
|
18 |
(defvar org-agenda-overriding-header nil) |
|
19 |
(defvar org-agenda-title-append nil) |
|
20 |
#@63 List of undoable operations in the agenda since last refresh. |
|
21 |
(defvar org-agenda-undo-list nil (#$ . 620)) |
|
22 |
#@73 In a series of undo commands, this is the list of remaining undo items. |
|
23 |
(defvar org-agenda-pending-undo-list nil (#$ . 733)) |
|
24 |
(byte-code "\300\301\302\303\304\305\306\307&\210\300\310\311\312\304\305\306\313&\210\300\314\315\316\304\305\306\317&\210\320\321\311\322\323\324\304\305&\210\300\325\326\327\304\321\306\313&\210\300\330\311\331\304\321\306\332&\210\300\333\334\335\304\321\306\336\337\340& \210\300\341\342\343\304\305\306\344&\210\300\345\326\346\304\305\306\313&\210\300\347\311\350\304\321\304\351\306\352& \210\300\353\311\354\304\305\306\313&\210\320\355\311\356\323\357\304\305&\207" [custom-declare-variable org-agenda-confirm-kill 1 "When set, remote killing from the agenda buffer needs confirmation.\nWhen t, a confirmation is always needed. When a number N, confirmation is\nonly needed when the text to be killed contains more than N non-white lines." :group org-agenda :type (choice (const :tag "Never" nil) (const :tag "Always" t) (integer :tag "When more than N lines")) org-agenda-compact-blocks nil "Non-nil means make the block agenda more compact.\nThis is done globally by leaving out lines like the agenda span\nname and week number or the separator lines." boolean org-agenda-block-separator 61 "The separator between blocks in the agenda.\nIf this is a string, it will be used as the separator, with a newline added.\nIf it is a character, it will be repeated to fill the window width.\nIf nil the separator is disabled. In `org-agenda-custom-commands' this\naddresses the separator between the current and the previous block." (choice (const :tag "Disabled" nil) (character) (string)) custom-declare-group org-agenda-export "Options concerning exporting agenda views in Org mode." :tag "Org Agenda Export" org-agenda-with-colors t "Non-nil means use colors in agenda views." org-agenda-exporter-settings "Alist of variable/value pairs that should be active during agenda export.\nThis is a good place to set options for ps-print and for htmlize.\nNote that the way this is implemented, the values will be evaluated\nbefore assigned to the variables. So make sure to quote values you do\n*not* want evaluated, for example\n\n (setq org-agenda-exporter-settings\n \\='((ps-print-color-p \\='black-white)))" (repeat (list (variable) (sexp :tag "Value"))) org-agenda-before-write-hook '(org-agenda-add-entry-text) "Hook run in a temporary buffer before writing the agenda to an export file.\nA useful function for this hook is `org-agenda-add-entry-text'." hook :options (org-agenda-add-entry-text) org-agenda-add-entry-text-maxlines 0 "Maximum number of entry text lines to be added to agenda.\nThis is only relevant when `org-agenda-add-entry-text' is part of\n`org-agenda-before-write-hook', which is the default.\nWhen this is 0, nothing will happen. When it is greater than 0, it\nspecifies the maximum number of lines that will be added for each entry\nthat is listed in the agenda view.\n\nNote that this variable is not used during display, only when exporting\nthe agenda. For agenda display, see the variables `org-agenda-entry-text-mode'\nand `org-agenda-entry-text-maxlines'." integer org-agenda-add-entry-text-descriptive-links "Non-nil means export org-links as descriptive links in agenda added text.\nThis variable applies to the text added to the agenda when\n`org-agenda-add-entry-text-maxlines' is larger than 0.\nWhen this variable nil, the URL will (also) be shown." org-agenda-export-html-style "The style specification for exported HTML Agenda files.\nIf this variable contains a string, it will replace the default <style>\nsection as produced by `htmlize'.\nSince there are different ways of setting style information, this variable\nneeds to contain the full HTML structure to provide a style, including the\nsurrounding HTML tags. The style specifications should include definitions\nthe fonts used by the agenda, here is an example:\n\n <style type=\"text/css\">\n p { font-weight: normal; color: gray; }\n .org-agenda-structure {\n font-size: 110%;\n color: #003399;\n font-weight: 600;\n }\n .org-todo {\n color: #cc6666;\n font-weight: bold;\n }\n .org-agenda-done {\n color: #339933;\n }\n .org-done {\n color: #339933;\n }\n .title { text-align: center; }\n .todo, .deadline { color: red; }\n .done { color: green; }\n </style>\n\nor, if you want to keep the style in a file,\n\n <link rel=\"stylesheet\" type=\"text/css\" href=\"mystyles.css\">\n\nAs the value of this option simply gets inserted into the HTML <head> header,\nyou can \"misuse\" it to also add other text to the header." org-export-html (choice (const nil) (string)) org-agenda-persistent-filter "When set, keep filters from one agenda view to the next." org-agenda-custom-commands "Options concerning agenda views in Org mode." "Org Agenda Custom Commands"] 10) |
|
25 |
#@18 Sorting choices. |
|
26 |
(defconst org-sorting-choice '(choice (const time-up) (const time-down) (const timestamp-up) (const timestamp-down) (const scheduled-up) (const scheduled-down) (const deadline-up) (const deadline-down) (const ts-up) (const ts-down) (const tsia-up) (const tsia-down) (const category-keep) (const category-up) (const category-down) (const tag-down) (const tag-up) (const priority-up) (const priority-down) (const todo-state-up) (const todo-state-down) (const effort-up) (const effort-down) (const habit-up) (const habit-down) (const alpha-up) (const alpha-down) (const user-defined-up) (const user-defined-down)) (#$ . 5702)) |
|
27 |
(byte-code "\300\301\302\"\210\300\303\304\"\207" [defvaralias org-agenda-filter-preset org-agenda-tag-filter-preset org-agenda-filter org-agenda-tag-filter] 3) |
|
28 |
#@1621 List of types searched for when creating the daily/weekly agenda. |
|
29 |
This variable is a list of symbols that controls the types of |
|
30 |
items that appear in the daily/weekly agenda. Allowed symbols in this |
|
31 |
list are are |
|
32 |
|
|
33 |
:timestamp List items containing a date stamp or date range matching |
|
34 |
the selected date. This includes sexp entries in angular |
|
35 |
brackets. |
|
36 |
|
|
37 |
:sexp List entries resulting from plain diary-like sexps. |
|
38 |
|
|
39 |
:deadline List deadline due on that date. When the date is today, |
|
40 |
also list any deadlines past due, or due within |
|
41 |
`org-deadline-warning-days'. |
|
42 |
|
|
43 |
:deadline* Same as above, but only include the deadline if it has an |
|
44 |
hour specification as [h]h:mm. |
|
45 |
|
|
46 |
:scheduled List all items which are scheduled for the given date. |
|
47 |
The diary for *today* also contains items which were |
|
48 |
scheduled earlier and are not yet marked DONE. |
|
49 |
|
|
50 |
:scheduled* Same as above, but only include the scheduled item if it |
|
51 |
has an hour specification as [h]h:mm. |
|
52 |
|
|
53 |
By default, all four non-starred types are turned on. |
|
54 |
|
|
55 |
When :scheduled* or :deadline* are included, :schedule or :deadline |
|
56 |
will be ignored. |
|
57 |
|
|
58 |
Never set this variable globally using `setq', because then it |
|
59 |
will apply to all future agenda commands. Instead, bind it with |
|
60 |
`let' to scope it dynamically into the agenda-constructing |
|
61 |
command. A good way to set it is through options in |
|
62 |
`org-agenda-custom-commands'. For a more flexible (though |
|
63 |
somewhat less efficient) way of determining what is included in |
|
64 |
the daily/weekly agenda, see `org-agenda-skip-function'. |
|
65 |
(defvar org-agenda-entry-types '(:deadline :scheduled :timestamp :sexp) (#$ . 6512)) |
|
66 |
#@127 Selection of examples for agenda command settings. |
|
67 |
This will be spliced into the custom type of |
|
68 |
`org-agenda-custom-commands'. |
|
69 |
(defconst org-agenda-custom-commands-local-options (byte-code "\302\303\304\305\303\306\307\310\311\303\312\313\311\314\302DE\257\315\316\317\320\321\322\323\324\325\326\311\303\327\330\311\331\332\333\334\335 \336BBBBBE\257\337BBBBBBBBBBBBBBBBBF\207" [org-sorting-choice org-agenda-entry-types repeat :tag "Local settings for this command. Remember to quote values" choice "Setting" (list :tag "Heading for this block" (const org-agenda-overriding-header) (string :tag "Headline")) (list :tag "Files to be searched" (const org-agenda-files) (list (const :format #1="" quote) (repeat (file)))) list "Sorting strategy" (const org-agenda-sorting-strategy) (const :format #1# quote) (list :tag "Prefix format" (const org-agenda-prefix-format :value " %-12:c%?-12t% s") (string)) (list :tag "Number of days in agenda" (const org-agenda-span) (list (const :format #1# quote) (choice (const :tag "Day" day) (const :tag "Week" week) (const :tag "Fortnight" fortnight) (const :tag "Month" month) (const :tag "Year" year) (integer :tag "Custom")))) (list :tag "Fixed starting date" (const org-agenda-start-day) (string :value "2007-11-01")) (list :tag "Start on day of week" (const org-agenda-start-on-weekday) (choice :value 1 (const :tag "Today" nil) (integer :tag "Weekday No."))) (list :tag "Include data from diary" (const org-agenda-include-diary) (boolean)) (list :tag "Deadline Warning days" (const org-deadline-warning-days) (integer :value 1)) (list :tag "Category filter preset" (const org-agenda-category-filter-preset) (list (const :format #1# quote) (repeat (string :tag "+category or -category")))) (list :tag "Tags filter preset" (const org-agenda-tag-filter-preset) (list (const :format #1# quote) (repeat (string :tag "+tag or -tag")))) (list :tag "Effort filter preset" (const org-agenda-effort-filter-preset) (list (const :format #1# quote) (repeat (string :tag "+=10 or -=10 or +<10 or ->10")))) (list :tag "Regexp filter preset" (const org-agenda-regexp-filter-preset) (list (const :format #1# quote) (repeat (string :tag "+regexp or -regexp")))) "Set daily/weekly entry types" (const org-agenda-entry-types) (const :format #1# quote) set :greedy t :value ((const :deadline) (const :scheduled) (const :deadline*) (const :scheduled*) (const :timestamp) (const :sexp)) ((list :tag "Standard skipping condition" :value (org-agenda-skip-function '(org-agenda-skip-entry-if)) (const org-agenda-skip-function) (list (const :format #1# quote) (list (choice :tag "Skipping range" (const :tag "Skip entry" org-agenda-skip-entry-if) (const :tag "Skip subtree" org-agenda-skip-subtree-if)) (repeat :inline t :tag "Conditions for skipping" (choice :tag "Condition type" (list :tag "Regexp matches" :inline t (const :format #1# regexp) (regexp)) (list :tag "Regexp does not match" :inline t (const :format #1# notregexp) (regexp)) (list :tag "TODO state is" :inline t (const todo) (choice (const :tag "Any not-done state" todo) (const :tag "Any done state" done) (const :tag "Any state" any) (list :tag "Keyword list" (const :format #1# quote) (repeat (string :tag "Keyword"))))) (list :tag "TODO state is not" :inline t (const nottodo) (choice (const :tag "Any not-done state" todo) (const :tag "Any done state" done) (const :tag "Any state" any) (list :tag "Keyword list" (const :format #1# quote) (repeat (string :tag "Keyword"))))) (const :tag "scheduled" scheduled) (const :tag "not scheduled" notscheduled) (const :tag "deadline" deadline) (const :tag "no deadline" notdeadline) (const :tag "timestamp" timestamp) (const :tag "no timestamp" nottimestamp)))))) (list :tag "Non-standard skipping condition" :value (org-agenda-skip-function) (const org-agenda-skip-function) (sexp :tag "Function or form (quoted!)")) (list :tag "Any variable" (variable :tag "Variable") (sexp :tag "Value (sexp)")))] 31) (#$ . 8224)) |
|
70 |
(byte-code "\301\302\303\304\305\302\306\307\310\311\312\313\314\315\316\317\320\321\322BBBBBBBB\313\314\323\324\325\307\314\326\310\313\314\327\330\331\257\313\314\332\333\334\257\313\314\335\336\337\257\313\314\340\341\342\257\313\314\343\344\345\257\313\314\346\347\350\257\313\314\351\352\353\257\313\314\354\355\356\257\257 F\357BBBBBB\360BBBBBD&\210\301\361\362\363\305\302\306\364&\210\301\365\366\367\305\302\306\370&\210\371\372\373\374\314\375\305\376&\210\301\377\373\201@ \305\372\306\201A &\210\371\201B \373\201C \314\201D \305\376&\210\371\201E \373\201F \314\201G \305\376&\210\371\201H \373\201I \314\201J \305\376&\210\371\201K \373\201L \314\201M \305\376&\207" [org-agenda-custom-commands-local-options custom-declare-variable org-agenda-custom-commands '(("n" "Agenda and all TODOs" ((agenda #1="") (alltodo #1#)))) "Custom commands for the agenda.\n\\<org-mode-map>\nThese commands will be offered on the splash screen displayed by the\nagenda dispatcher `\\[org-agenda]'. Each entry is a list like this:\n\n (key desc type match settings files)\n\nkey The key (one or more characters as a string) to be associated\n with the command.\ndesc A description of the command, when omitted or nil, a default\n description is built using MATCH.\ntype The command type, any of the following symbols:\n agenda The daily/weekly agenda.\n todo Entries with a specific TODO keyword, in all agenda files.\n search Entries containing search words entry or headline.\n tags Tags/Property/TODO match in all agenda files.\n tags-todo Tags/P/T match in all agenda files, TODO entries only.\n todo-tree Sparse tree of specific TODO keyword in *current* file.\n tags-tree Sparse tree with all tags matches in *current* file.\n occur-tree Occur sparse tree for *current* file.\n ... A user-defined function.\nmatch What to search for:\n - a single keyword for TODO keyword searches\n - a tags match expression for tags searches\n - a word search expression for text searches.\n - a regular expression for occur searches\n For all other commands, this should be the empty string.\nsettings A list of option settings, similar to that in a let form, so like\n this: ((opt1 val1) (opt2 val2) ...). The values will be\n evaluated at the moment of execution, so quote them when needed.\nfiles A list of files to write the produced agenda buffer to with\n the command `org-store-agenda-views'.\n If a file name ends in \".html\", an HTML version of the buffer\n is written out. If it ends in \".ps\", a postscript version is\n produced. Otherwise, only the plain text is written to the file.\n\nYou can also define a set of commands, to create a composite agenda buffer.\nIn this case, an entry looks like this:\n\n (key desc (cmd1 cmd2 ...) general-settings-for-whole-set files)\n\nwhere\n\ndesc A description string to be displayed in the dispatcher menu.\ncmd An agenda command, similar to the above. However, tree commands\n are not allowed, but instead you can get agenda and global todo list.\n So valid commands for a set are:\n (agenda \"\" settings)\n (alltodo \"\" settings)\n (stuck \"\" settings)\n (todo \"match\" settings files)\n (search \"match\" settings files)\n (tags \"match\" settings files)\n (tags-todo \"match\" settings files)\n\nEach command can carry a list of options, and another set of options can be\ngiven for the whole set of commands. Individual command options take\nprecedence over the general options.\n\nWhen using several characters as key to a command, the first characters\nare prefix commands. For the dispatcher to display useful information, you\nshould provide a description for the prefix, like\n\n (setq org-agenda-custom-commands\n \\='((\"h\" . \"HOME + Name tag searches\") ; describe prefix \"h\"\n (\"hl\" tags \"+HOME+Lisa\")\n (\"hp\" tags \"+HOME+Peter\")\n (\"hk\" tags \"+HOME+Kim\")))" :group :type repeat choice :value ("x" "Describe command here" tags #1# nil) list :tag "Single command" (string :tag "Access Key(s) ") (option (string :tag "Description")) (choice (const :tag "Agenda" agenda) (const :tag "TODO list" alltodo) (const :tag "Search words" search) (const :tag "Stuck projects" stuck) (const :tag "Tags/Property match (all agenda files)" tags) (const :tag "Tags/Property match of TODO entries (all agenda files)" tags-todo) (const :tag "TODO keyword search (all agenda files)" todo) (const :tag "Tags sparse tree (current buffer)" tags-tree) (const :tag "TODO keyword tree (current buffer)" todo-tree) (const :tag "Occur tree (current buffer)" occur-tree) (sexp :tag "Other, user-defined function")) (string :tag "Match (only for some commands)") ((option (repeat :tag "Export" (file :tag "Export to")))) "Command series, all agenda files" (string :tag "Access Key(s)") (string :tag "Description ") "Component" "Agenda" (const :format #1# agenda) (const :tag #1# :format #1# #1#) "TODO list (all keywords)" (const :format #1# alltodo) (const :tag #1# :format #1# #1#) "Search words" (const :format #1# search) (string :tag "Match") "Stuck projects" (const :format #1# stuck) (const :tag #1# :format #1# #1#) "Tags search" (const :format #1# tags) (string :tag "Match") "Tags search, TODO entries only" (const :format #1# tags-todo) (string :tag "Match") "TODO keyword search" (const :format #1# todo) (string :tag "Match") "Other, user-defined function" (symbol :tag "function") (string :tag "Match") ((repeat :tag "Settings for entire command set" (list (variable :tag "Any variable") (sexp :tag "Value"))) (option (repeat :tag "Export" (file :tag "Export to")))) ((cons :tag "Prefix key documentation" (string :tag "Access Key(s)") (string :tag "Description "))) org-agenda-query-register 111 "The register holding the current query string.\nThe purpose of this is that if you construct a query string interactively,\nyou can then use it to define a custom command." character org-stuck-projects '("+LEVEL=2/-DONE" ("TODO" "NEXT" "NEXTACTION") nil #1#) "How to identify stuck projects.\nThis is a list of four items:\n1. A tags/todo/property matcher string that is used to identify a project.\n See the manual for a description of tag and property searches.\n The entire tree below a headline matched by this is considered one project.\n2. A list of TODO keywords identifying non-stuck projects.\n If the project subtree contains any headline with one of these todo\n keywords, the project is considered to be not stuck. If you specify\n \"*\" as a keyword, any TODO keyword will mark the project unstuck.\n3. A list of tags identifying non-stuck projects.\n If the project subtree contains any headline with one of these tags,\n the project is considered to be not stuck. If you specify \"*\" as\n a tag, any tag will mark the project unstuck. Note that this is about\n the explicit presence of a tag somewhere in the subtree, inherited\n tags do not count here. If inherited tags make a project not stuck,\n use \"-TAG\" in the tags part of the matcher under (1.) above.\n4. An arbitrary regular expression matching non-stuck projects.\n\nIf the project turns out to be not stuck, search continues also in the\nsubtree to see if any of the subtasks have project status.\n\nSee also the variable `org-tags-match-list-sublevels' which applies\nto projects matched by this search as well.\n\nAfter defining this variable, you may use `org-agenda-list-stuck-projects'\n(bound to `\\[org-agenda] #') to produce the list." (list (string :tag "Tags/TODO match to identify a project") (repeat :tag "Projects are *not* stuck if they have an entry with TODO keyword any of" (string)) (repeat :tag "Projects are *not* stuck if they have an entry with TAG being any of" (string)) (regexp :tag "Projects are *not* stuck if this regexp matches inside the subtree")) custom-declare-group org-agenda-skip nil "Options concerning skipping parts of agenda files." "Org Agenda Skip" org-agenda org-agenda-skip-function-global "Function to be called at each match during agenda construction.\nIf this function returns nil, the current match should not be skipped.\nIf the function decided to skip an agenda match, is must return the\nbuffer position from which the search should be continued.\nThis may also be a Lisp form, which will be evaluated.\n\nThis variable will be applied to every agenda match, including\ntags/property searches and TODO lists. So try to make the test function\ndo its checking as efficiently as possible. To implement a skipping\ncondition just for specific agenda commands, use the variable\n`org-agenda-skip-function' which can be set in the options section\nof custom agenda commands." sexp org-agenda-daily/weekly "Options concerning the daily/weekly agenda." "Org Agenda Daily/Weekly" org-agenda-todo-list "Options concerning the global todo list agenda view." "Org Agenda Todo List" org-agenda-match-view "Options concerning the general tags/property/todo match agenda view." "Org Agenda Match View" org-agenda-search-view "Options concerning the search agenda view." "Org Agenda Search View"] 34) |
|
71 |
#@295 Non-nil means the agenda will include archived items. |
|
72 |
If this is the symbol `trees', trees in the selected agenda scope |
|
73 |
that are marked with the ARCHIVE tag will be included anyway. When this is |
|
74 |
t, also all archive files associated with the current selection of agenda |
|
75 |
files will be included. |
|
76 |
(defvar org-agenda-archives-mode nil (#$ . 21560)) |
|
77 |
(byte-code "\300\301\302\303\304\305\306\307&\210\300\310\302\311\304\312\306\307&\210\300\313\302\314\304\312\304\315\306\307& \210\300\316\317\320\304\312\304\315\306\307& \210\300\321\317\322\304\312\304\315\323\324\306\325&\210\300\326\317\327\304\312\304\315\306\330& \210\300\331\317\332\304\312\304\315\306\333& \210\300\334\317\335\304\312\304\315\323\336\337\340\306\341&
\210\300\342\317\343\304\312\304\315\304\344\306\307&\210\300\345\317\346\304\312\304\347\306\307& \210\300\350\317\351\304\312\304\347\306\352& \210\300\353\317\354\304\312\304\347\323\324\306\355&\210\300\356\317\357\304\312\304\347\306\307& \210\300\360\317\361\304\312\304\347\323\324\306\362&\210\300\363\317\364\304\312\304\347\323\336\337\365\306\366&
\210\300\367\317\370\304\312\306\307&\210\300\371\317\372\304\312\304\347\306\307& \210\300\373\302\374\304\347\304\315\323\375\306\376&\210\377\201@ \317\201A \201B \201C \304\305&\210\300\201D \302\201E \304\305\323\324\306\307& \210\300\201F \317\201G \304\305\323\324\306\307& \210\300\201H \317\201I \304\201@ \306\201J &\210\300\201K \317\201L \304\201@ \306\307&\210\300\201M \317\201N \304\201@ \306\307&\210\300\201O \317\201P \304\305\323\324\306\307& \210\300\201Q \302\201R \304\201@ \306\307&\210\300\201S \317\201T \304\201@ \306\307&\210\300\201U \201V \201W \304\305\306\201X &\210\300\201Y \317\201Z \304\305\306\201[ &\210\300\201\\ \201] \201^ \323\336\337\201_ \304\305\306\201` &\207" [custom-declare-variable org-agenda-restriction-lock-highlight-subtree t "Non-nil means highlight the whole subtree when restriction is active.\nOtherwise only highlight the headline. Highlighting the whole subtree is\nuseful to ensure no edits happen beyond the restricted region." :group org-agenda :type boolean org-agenda-skip-comment-trees "Non-nil means skip trees that start with the COMMENT keyword.\nWhen nil, these trees are also scanned by agenda commands." org-agenda-skip org-agenda-todo-list-sublevels "Non-nil means check also the sublevels of a TODO entry for TODO entries.\nWhen nil, the sublevels of a TODO entry are not checked, resulting in\npotentially much shorter TODO lists." org-agenda-todo-list org-agenda-todo-ignore-with-date nil "Non-nil means don't show entries with a date in the global todo list.\nYou can use this if you prefer to mark mere appointments with a TODO keyword,\nbut don't want them to show up in the TODO list.\nWhen this is set, it also covers deadlines and scheduled items, the settings\nof `org-agenda-todo-ignore-scheduled' and `org-agenda-todo-ignore-deadlines'\nwill be ignored.\nSee also the variable `org-agenda-tags-todo-honor-ignore-options'." org-agenda-todo-ignore-timestamp "Non-nil means don't show entries with a timestamp.\nThis applies when creating the global todo list.\nValid values are:\n\npast Don't show entries for today or in the past.\n\nfuture Don't show entries with a timestamp in the future.\n The idea behind this is that if it has a future\n timestamp, you don't want to think about it until the\n date.\n\nall Don't show any entries with a timestamp in the global todo list.\n The idea behind this is that by setting a timestamp, you\n have already \"taken care\" of this item.\n\nThis variable can also have an integer as a value. If positive (N),\ntodos with a timestamp N or more days in the future will be ignored. If\nnegative (-N), todos with a timestamp N or more days in the past will be\nignored. If 0, todos with a timestamp either today or in the future will\nbe ignored. For example, a value of -1 will exclude todos with a\ntimestamp in the past (yesterday or earlier), while a value of 7 will\nexclude todos with a timestamp a week or more in the future.\n\nSee also `org-agenda-todo-ignore-with-date'.\nSee also the variable `org-agenda-tags-todo-honor-ignore-options' if you want\nto make his option also apply to the tags-todo list." :version "24.1" (choice (const :tag "Ignore future timestamp todos" future) (const :tag "Ignore past or present timestamp todos" past) (const :tag "Ignore all timestamp todos" all) (const :tag "Show timestamp todos" nil) (integer :tag "Ignore if N or more days in past(-) or future(+).")) org-agenda-todo-ignore-scheduled "Non-nil means, ignore some scheduled TODO items when making TODO list.\nThis applies when creating the global todo list.\nValid values are:\n\npast Don't show entries scheduled today or in the past.\n\nfuture Don't show entries scheduled in the future.\n The idea behind this is that by scheduling it, you don't want to\n think about it until the scheduled date.\n\nall Don't show any scheduled entries in the global todo list.\n The idea behind this is that by scheduling it, you have already\n \"taken care\" of this item.\n\nt Same as `all', for backward compatibility.\n\nThis variable can also have an integer as a value. See\n`org-agenda-todo-ignore-timestamp' for more details.\n\nSee also `org-agenda-todo-ignore-with-date'.\nSee also the variable `org-agenda-tags-todo-honor-ignore-options' if you want\nto make his option also apply to the tags-todo list." (choice (const :tag "Ignore future-scheduled todos" future) (const :tag "Ignore past- or present-scheduled todos" past) (const :tag "Ignore all scheduled todos" all) (const :tag "Ignore all scheduled todos (compatibility)" t) (const :tag "Show scheduled todos" nil) (integer :tag "Ignore if N or more days in past(-) or future(+).")) org-agenda-todo-ignore-deadlines "Non-nil means ignore some deadline TODO items when making TODO list.\n\nThere are different motivations for using different values, please think\ncarefully when configuring this variable.\n\nThis applies when creating the global TODO list.\n\nValid values are:\n\nnear Don't show near deadline entries. A deadline is near when it is\n closer than `org-deadline-warning-days' days. The idea behind this\n is that such items will appear in the agenda anyway.\n\nfar Don't show TODO entries where a deadline has been defined, but\n is not going to happen anytime soon. This is useful if you want to use\n the TODO list to figure out what to do now.\n\npast Don't show entries with a deadline timestamp for today or in the past.\n\nfuture Don't show entries with a deadline timestamp in the future, not even\n when they become `near' ones. Use it with caution.\n\nall Ignore all TODO entries that do have a deadline.\n\nt Same as `near', for backward compatibility.\n\nThis variable can also have an integer as a value. See\n`org-agenda-todo-ignore-timestamp' for more details.\n\nSee also `org-agenda-todo-ignore-with-date'.\nSee also the variable `org-agenda-tags-todo-honor-ignore-options' if you want\nto make his option also apply to the tags-todo list." (choice (const :tag "Ignore near deadlines" near) (const :tag "Ignore near deadlines (compatibility)" t) (const :tag "Ignore far deadlines" far) (const :tag "Ignore all TODOs with a deadlines" all) (const :tag "Show all TODOs, even if they have a deadline" nil) (integer :tag "Ignore if N or more days in past(-) or future(+).")) org-agenda-todo-ignore-time-comparison-use-seconds "Time unit to use when possibly ignoring an agenda item.\n\nSee the docstring of various `org-agenda-todo-ignore-*' options.\nThe default is to compare time stamps using days. An item is thus\nconsidered to be in the future if it is at least one day after today.\nNon-nil means to compare time stamps using seconds. An item is then\nconsidered future if it has a time value later than current time." "24.4" :package-version (Org . "8.0") (choice (const :tag "Compare time with days" nil) (const :tag "Compare time with seconds" t)) org-agenda-tags-todo-honor-ignore-options "Non-nil means honor todo-list ignores options also in tags-todo search.\nThe variables\n `org-agenda-todo-ignore-with-date',\n `org-agenda-todo-ignore-timestamp',\n `org-agenda-todo-ignore-scheduled',\n `org-agenda-todo-ignore-deadlines'\nmake the global TODO list skip entries that have time stamps of certain\nkinds. If this option is set, the same options will also apply for the\ntags-todo search, which is the general tags/property matcher\nrestricted to unfinished TODO entries only." org-agenda-match-view org-agenda-skip-scheduled-if-done "Non-nil means don't show scheduled items in agenda when they are done.\nThis is relevant for the daily/weekly agenda, not for the TODO list. It\napplies only to the actual date of the scheduling. Warnings about an item\nwith a past scheduling dates are always turned off when the item is DONE." org-agenda-daily/weekly org-agenda-skip-scheduled-if-deadline-is-shown "Non-nil means skip scheduling line if same entry shows because of deadline.\n\nIn the agenda of today, an entry can show up multiple times\nbecause it is both scheduled and has a nearby deadline, and maybe\na plain time stamp as well.\n\nWhen this variable is nil, the entry will be shown several times.\n\nWhen set to t, then only the deadline is shown and the fact that\nthe entry is scheduled today or was scheduled previously is not\nshown.\n\nWhen set to the symbol `not-today', skip scheduled previously,\nbut not scheduled today.\n\nWhen set to the symbol `repeated-after-deadline', skip scheduled\nitems if they are repeated beyond the current deadline." (choice (const :tag "Never" nil) (const :tag "Always" t) (const :tag "Not when scheduled today" not-today) (const :tag "When repeated past deadline" repeated-after-deadline)) org-agenda-skip-timestamp-if-deadline-is-shown "Non-nil means skip timestamp line if same entry shows because of deadline.\nIn the agenda of today, an entry can show up multiple times\nbecause it has both a plain timestamp and has a nearby deadline.\nWhen this variable is t, then only the deadline is shown and the\nfact that the entry has a timestamp for or including today is not\nshown. When this variable is nil, the entry will be shown\nseveral times." (choice (const :tag "Never" nil) (const :tag "Always" t)) org-agenda-skip-deadline-if-done "Non-nil means don't show deadlines when the corresponding item is done.\nWhen nil, the deadline is still shown and should give you a happy feeling.\nThis is relevant for the daily/weekly agenda. It applies only to the\nactual date of the deadline. Warnings about approaching and past-due\ndeadlines are always turned off when the item is DONE." org-agenda-skip-deadline-prewarning-if-scheduled "Non-nil means skip deadline prewarning when entry is also scheduled.\nThis will apply on all days where a prewarning for the deadline would\nbe shown, but not at the day when the entry is actually due. On that day,\nthe deadline will be shown anyway.\nThis variable may be set to nil, t, the symbol `pre-scheduled',\nor a number which will then give the number of days before the actual\ndeadline when the prewarnings should resume. The symbol `pre-scheduled'\neliminates the deadline prewarning only prior to the scheduled date.\nThis can be used in a workflow where the first showing of the deadline will\ntrigger you to schedule it, and then you don't want to be reminded of it\nbecause you will take care of it on the day when scheduled." (choice (const :tag "Always show prewarning" nil) (const :tag "Remove prewarning prior to scheduled date" pre-scheduled) (const :tag "Remove prewarning if entry is scheduled" t) (integer :tag "Restart prewarning N days before deadline")) org-agenda-skip-scheduled-delay-if-deadline "Non-nil means skip scheduled delay when entry also has a deadline.\nThis variable may be set to nil, t, the symbol `post-deadline',\nor a number which will then give the number of days after the actual\nscheduled date when the delay should expire. The symbol `post-deadline'\neliminates the schedule delay when the date is posterior to the deadline." (Org . "8.0") (choice (const :tag "Always honor delay" nil) (const :tag "Ignore delay if posterior to the deadline" post-deadline) (const :tag "Ignore delay if entry has a deadline" t) (integer :tag "Honor delay up until N days after the scheduled date")) org-agenda-skip-additional-timestamps-same-entry "When nil, multiple same-day timestamps in entry make multiple agenda lines.\nWhen non-nil, after the search for timestamps has matched once in an\nentry, the rest of the entry will not be searched." org-agenda-skip-timestamp-if-done "Non-nil means don't select item by timestamp or -range if it is DONE." org-agenda-dim-blocked-tasks "Non-nil means dim blocked tasks in the agenda display.\nThis causes some overhead during agenda construction, but if you\nhave turned on `org-enforce-todo-dependencies',\n`org-enforce-todo-checkbox-dependencies', or any other blocking\nmechanism, this will create useful feedback in the agenda.\n\nInstead of t, this variable can also have the value `invisible'.\nThen blocked tasks will be invisible and only become visible when\nthey become unblocked. An exemption to this behavior is when a task is\nblocked because of unchecked checkboxes below it. Since checkboxes do\nnot show up in the agenda views, making this task invisible you remove any\ntrace from agenda views that there is something to do. Therefore, a task\nthat is blocked because of checkboxes will never be made invisible, it\nwill only be dimmed." "24.3" (choice (const :tag "Do not dim" nil) (const :tag "Dim to a gray face" t) (const :tag "Make invisible" invisible)) custom-declare-group org-agenda-startup "Options concerning initial settings in the Agenda in Org Mode." :tag "Org Agenda Startup" org-agenda-menu-show-matcher "Non-nil means show the match string in the agenda dispatcher menu.\nWhen nil, the matcher string is not shown, but is put into the help-echo\nproperty so than moving the mouse over the command shows it.\nSetting it to nil is good if matcher strings are very long and/or if\nyou want to use two-columns display (see `org-agenda-menu-two-columns')." org-agenda-menu-two-columns "Non-nil means, use two columns to show custom commands in the dispatcher.\nIf you use this, you probably want to set `org-agenda-menu-show-matcher'\nto nil." org-agenda-finalize-hook "Hook run just before displaying an agenda buffer.\nThe buffer is still writable when the hook is called.\n\nYou can modify some of the buffer substrings but you should be\nextra careful not to modify the text properties of the agenda\nheadlines as the agenda display heavily relies on them." hook org-agenda-mouse-1-follows-link "Non-nil means mouse-1 on a link will follow the link in the agenda.\nA longer mouse click will still set point. Needs to be set\nbefore org.el is loaded." org-agenda-start-with-follow-mode "The initial value of follow mode in a newly created agenda window." org-agenda-follow-indirect "Non-nil means `org-agenda-follow-mode' displays only the\ncurrent item's tree, in an indirect buffer." org-agenda-show-outline-path "Non-nil means show outline path in echo area after line motion." org-agenda-start-with-entry-text-mode "The initial value of entry-text-mode in a newly created agenda window." org-agenda-entry-text-maxlines 5 "Number of text lines to be added when `E' is pressed in the agenda.\n\nNote that this variable only used during agenda display. To add entry text\nwhen exporting the agenda, configure the variable\n`org-agenda-add-entry-text-maxlines'." integer org-agenda-entry-text-exclude-regexps "List of regular expressions to clean up entry text.\nThe complete matches of all regular expressions in this list will be\nremoved from entry text before it is shown in the agenda." (repeat (regexp)) org-agenda-entry-text-leaders " > " "Text prepended to the entry text in agenda buffers." (Org . "8.0") string] 14) |
|
78 |
#@386 Hook that is run after basic cleanup of entry text to be shown in agenda. |
|
79 |
This cleanup is done in a temporary buffer, so the function may inspect and |
|
80 |
change the entire buffer. |
|
81 |
Some default stuff like drawers and scheduling/deadline dates will already |
|
82 |
have been removed when this is called, as will any matches for regular |
|
83 |
expressions listed in `org-agenda-entry-text-exclude-regexps'. |
|
84 |
(defvar org-agenda-entry-text-cleanup-hook nil (#$ . 37709)) |
|
85 |
#@75 Non-nil means include inactive time stamps in agenda. |
|
86 |
Dynamically scoped. |
|
87 |
(defvar org-agenda-include-inactive-timestamps nil (#$ . 38161)) |
|
88 |
(byte-code "\300\301\302\303\304\305\306\307&\210\310\311\312\313\306\301\314\315&\210\310\316\317\320\306\301\314\321&\210\310\322\302\323\306\301\314\324&\210\310\325\326\327\306\330\314\331&\210\310\332\333\334\306\330\314\335&\210\310\336\337\340\306\330\314\324&\210\310\341\342\343\306\330\314\344&\207" [custom-declare-group org-agenda-windows nil "Options concerning the windows used by the Agenda in Org Mode." :tag "Org Agenda Windows" :group org-agenda custom-declare-variable org-agenda-window-setup 'reorganize-frame "How the agenda buffer should be displayed.\nPossible values for this option are:\n\ncurrent-window Show agenda in the current window, keeping all other windows.\nother-window Use `switch-to-buffer-other-window' to display agenda.\nonly-window Show agenda, deleting all other windows.\nreorganize-frame Show only two windows on the current frame, the current\n window and the agenda.\nother-frame Use `switch-to-buffer-other-frame' to display agenda.\n Also, when exiting the agenda, kill that frame.\nSee also the variable `org-agenda-restore-windows-after-quit'." :type (choice (const current-window) (const other-frame) (const other-window) (const only-window) (const reorganize-frame)) org-agenda-window-frame-fractions '(0.5 . 0.75) "The min and max height of the agenda window as a fraction of frame height.\nThe value of the variable is a cons cell with two numbers between 0 and 1.\nIt only matters if `org-agenda-window-setup' is `reorganize-frame'." (cons (number :tag "Minimum") (number :tag "Maximum")) org-agenda-restore-windows-after-quit "Non-nil means restore window configuration upon exiting agenda.\nBefore the window configuration is changed for displaying the agenda,\nthe current status is recorded. When the agenda is exited with\n`q' or `x' and this option is set, the old state is restored. If\n`org-agenda-window-setup' is `other-frame', the value of this\noption will be ignored." boolean org-agenda-span 'week "Number of days to include in overview display.\nCan be day, week, month, year, or any number of days.\nCustom commands can set this variable in the options section." org-agenda-daily/weekly (choice (const :tag "Day" day) (const :tag "Week" week) (const :tag "Fortnight" fortnight) (const :tag "Month" month) (const :tag "Year" year) (integer :tag "Custom")) org-agenda-start-on-weekday 1 "Non-nil means start the overview always on the specified weekday.\n0 denotes Sunday, 1 denotes Monday, etc.\nWhen nil, always start on the current day.\nCustom commands can set this variable in the options section." (choice (const :tag "Today" nil) (integer :tag "Weekday No.")) org-agenda-show-all-dates t "Non-nil means `org-agenda' shows every day in the selected range.\nWhen nil, only the days which actually have entries are shown." org-agenda-format-date 'org-agenda-format-date-aligned "Format string for displaying dates in the agenda.\nUsed by the daily/weekly agenda. This should be a format string\nunderstood by `format-time-string', or a function returning the\nformatted date as a string. The function must take a single\nargument, a calendar-style date list like (month day year)." (choice (string :tag "Format string") (function :tag "Function"))] 8) |
|
89 |
#@128 Format a DATE string for display in the daily/weekly agenda. |
|
90 |
This function makes sure that dates are aligned for easy reading. |
|
91 |
(defalias 'org-agenda-format-date-aligned #[(date) "\306\307!\210\310!A@\311!@\312\f!\3138#\314\211\3138)\315$\211#\316U\2036 \317\320!\202\250#\316V\203\277 #S$\321\211\211@)\211A@)\3138)#\n\fS\322_\\%\f\313V\203\247 %\323\f\324_\\\325\245Z%#\211#\316W\203\205 \326#!S##\324\246\316U\205\236 #\327\246\316U?\206\236 #\330\246\316U)\203\247 %T%%-$\331_$\324\245$\327\245[$\330\245%\202\250\326#T!$\332\211\211@)\211A@)\3138)#\n\fS\322_\\%\f\313V\203+%\323\f\324_\\\325\245Z%#\211#\316W\203 \326#!S##\324\246\316U\205\"#\327\246\316U?\206\"#\330\246\316U)\203+%T%%-$\331_$\324\245$\327\245[$\330\245\333\211\211@)\211A@)\3138)#\n\fS\322_\\%\f\313V\203\243%\323\f\324_\\\325\245Z%#\211#\316W\203\201\326#!S##\324\246\316U\205\232#\327\246\316U?\206\232#\330\246\316U)\203\243%T%%-&+!&\f\334U\203\277&\335Y\203\277#S\202\324\f\336U\203\322&\334X\203\322#T\202\324#'\334U\203\344\337\340&\"\202\345\341(\337\342 \n
#(&. \207" [date dayname day day-of-week month monthname require cal-iso calendar-day-name calendar-day-of-week calendar-month-name 2 org-days-to-iso-week nil 0 user-error "There was no year zero" + 31 23 4 10 abs 100 400 365 - (12 31 -1) 1 52 12 format " W%02d" "" "%-10s %2d %s %4d%s" year offset-years day-of-year iso-week weekyear weekstring] 12 (#$ . 41600)]) |
|
92 |
(byte-code "\300\301\302\303\304\305\306\307\310\311& \210\300\312\302\313\304\314\306\307\310\311& \207" [custom-declare-variable org-agenda-time-leading-zero nil "Non-nil means use leading zero for military times in agenda.\nFor example, 9:30am would become 09:30 rather than 9:30." :group org-agenda-daily/weekly :version "24.1" :type boolean org-agenda-timegrid-use-ampm "When set, show AM/PM style timestamps on the timegrid." org-agenda] 10) |
|
93 |
#@70 Convert TIME of a string like "13:45" to an AM/PM style time string. |
|
94 |
(defalias 'org-agenda-time-of-day-to-ampm #[(time) "\305\306\307O!\310\311O\312 \313\232\203 \314\202% \313V\203% \314 \313Z\f\2030 \315\316 \"\2026 \315\317\320 !\"\321\nR+\207" [time hour-number minute ampm org-agenda-time-leading-zero string-to-number 0 -3 -2 nil "am" 12 "pm" format "%02d" "%02s" number-to-string ":"] 4 (#$ . 43593)]) |
|
95 |
#@85 Conditionally convert TIME to AM/PM format based on `org-agenda-timegrid-use-ampm'. |
|
96 |
(defalias 'org-agenda-time-of-day-to-ampm-maybe #[(time) "\203 \302 !\207 \207" [org-agenda-timegrid-use-ampm time org-agenda-time-of-day-to-ampm] 2 (#$ . 44019)]) |
|
97 |
(byte-code "\301\302\303\304\305\306\307\310&\210\301\311\312\313\305\306\314\315\307\316& \210\301\317\320\321\305\306\307\316&\210\301\322\312\323\305\306\314\315\307\316& \210\301\324\312\325\305\306\307\326\314\327\330\331\332\333&
\210\301\334\320\335\305\306\307\336\314\327\330\337\332\340&
\210\301\341\342\343\305\306\307\344\332\345& \210\301\346\342\347\305\306\307\344\314\327\330\350\332\345&
\210\301\351\352\353\305\306\307\354&\210\301\355\356\357\305\306\305\360\314\315\307\361&\210\301\362\312\363\305\306\307\316&\210\301\364\320\365\305\366\305\306\307\367& \210\301\370\320\371\305\366\305\306\307\316& \210\301\372\373\374\305\306\307\361&\210\301\375\320\376\305\377\314\315\307\316& \210\201@ \201A \375\"\210\301\201B \320\201C \305\377\314\315\307\316& \210\301\201D \201E \201F \305\377\314\327\330\201G \307\344&\210\201H \201I \320\201J \201K \201L \305\201M &\210\301\201N \312\201O \305\201I \307\316&\210\301\201P \312\201Q \305\201I \307\316&\210\301\201I \201R \201S \305\201I \307\201T &\210\301\201U \312\201V \305\201I \314\315\307\316& \210\301\201W \201X \201Y \305\201I \314\315\307\201Z & \210\201H \201[ \320\201\\ \201K \201] \305\201M &\210\301\201^ \201_ \201` \305\201[ \307\201a \201b \201K \201c F\201d \201K \201e \201f \201g \201b DE\201f \201h \201b DE\201f \201i \201b DE\201f \201j \201b DE\257E&\210\301\201k \320\201l \305\201[ \307\201m &\210\301\201n \312\201o \305\201[ \307\316&\210\301\201p \312\201q \305\201[ \307\316&\210\201H \201r \320\201s \201K \201t \305\201M &\210\301\201u \201v \201w \307\201x \305\201r \314\327\330\201y &\207" [org-sorting-choice custom-declare-variable org-agenda-weekend-days '(6 0) "Which days are weekend?\nThese days get the special face `org-agenda-date-weekend' in the agenda." :group org-agenda-daily/weekly :type (set :greedy t (const :tag "Monday" 1) (const :tag "Tuesday" 2) (const :tag "Wednesday" 3) (const :tag "Thursday" 4) (const :tag "Friday" 5) (const :tag "Saturday" 6) (const :tag "Sunday" 0)) org-agenda-move-date-from-past-immediately-to-today t "Non-nil means jump to today when moving a past date forward in time.\nWhen using S-right in the agenda to move a a date forward, and the date\nstamp currently points to the past, the first key press will move it\nto today. WHen nil, just move one day forward even if the date stays\nin the past." :version "24.1" boolean org-agenda-include-diary nil "If non-nil, include in the agenda entries from the Emacs Calendar's diary.\nCustom commands can set this variable in the options section." org-agenda-include-deadlines "If non-nil, include entries within their deadline warning period.\nCustom commands can set this variable in the options section." org-agenda-show-future-repeats "Non-nil shows repeated entries in the future part of the agenda.\nWhen set to the symbol `next' only the first future repeat is shown." (choice (const :tag "Show all repeated entries" t) (const :tag "Show next repeated entry" next) (const :tag "Do not show repeated entries" nil)) "26.1" :package-version (Org . "9.1") :safe symbolp org-agenda-prefer-last-repeat "Non-nil sets date for repeated entries to their last repeat.\n\nWhen nil, display SCHEDULED and DEADLINE dates at their base\ndate, and in today's agenda, as a reminder. Display plain\ntime-stamps, on the other hand, at every repeat date in the past\nin addition to the base date.\n\nWhen non-nil, show a repeated entry at its latest repeat date,\npossibly being today even if it wasn't marked as done. This\nsetting is useful if you do not always mark repeated entries as\ndone and, yet, consider that reaching repeat date starts the task\nanew.\n\nWhen set to a list of strings, prefer last repeats only for\nentries with these TODO keywords." (choice (const :tag "Prefer last repeat" t) (const :tag "Prefer base date" nil) (repeat :tag "Prefer last repeat for entries with these TODO keywords" (string :tag "TODO keyword"))) (Org . "9.1") #[(x) "\301!\206 :\207" [x booleanp] 2] org-scheduled-past-days 10000 "Number of days to continue listing scheduled items not marked DONE.\nWhen an item is scheduled on a date, it shows up in the agenda on\nthis day and will be listed until it is marked done or for the\nnumber of days given here." integer integerp org-deadline-past-days "Number of days to warn about missed deadlines.\nWhen an item has deadline on a date, it shows up in the agenda on\nthis day and will appear as a reminder until it is marked DONE or\nfor the number of days given here." (Org . "9.1") org-agenda-log-mode-items '(closed clock) "List of items that should be shown in agenda log mode.\n\\<org-agenda-mode-map>This list may contain the following symbols:\n\n closed Show entries that have been closed on that day.\n clock Show entries that have received clocked time on that day.\n state Show all logged state changes.\nNote that instead of changing this variable, you can also press `\\[universal-argument] \\[org-agenda-log-mode]' in\nthe agenda to display all available LOG items temporarily." (set :greedy t (const closed) (const clock) (const state)) org-agenda-clock-consistency-checks '(:max-duration "10:00" :min-duration 0 :max-gap "0:05" :gap-ok-around ("4:00") :default-face ((:background "DarkRed") (:foreground "white")) :overlap-face nil :gap-face nil :no-end-time-face nil :long-face nil :short-face nil) "This is a property list, with the following keys:\n\n:max-duration Mark clocking chunks that are longer than this time.\n This is a time string like \"HH:MM\", or the number\n of minutes as an integer.\n\n:min-duration Mark clocking chunks that are shorter that this.\n This is a time string like \"HH:MM\", or the number\n of minutes as an integer.\n\n:max-gap Mark gaps between clocking chunks that are longer than\n this duration. A number of minutes, or a string\n like \"HH:MM\".\n\n:gap-ok-around List of times during the day which are usually not working\n times. When a gap is detected, but the gap contains any\n of these times, the gap is *not* reported. For example,\n if this is (\"4:00\" \"13:00\") then gaps that contain\n 4:00 in the morning (i.e. the night) and 13:00\n (i.e. a typical lunch time) do not cause a warning.\n You should have at least one time during the night in this\n list, or otherwise the first task each morning will trigger\n a warning because it follows a long gap.\n\nFurthermore, the following properties can be used to define faces for\nissue display.\n\n:default-face the default face, if the specific face is undefined\n:overlap-face face for overlapping clocks\n:gap-face face for gaps between clocks\n:no-end-time-face face for incomplete clocks\n:long-face face for clock intervals that are too long\n:short-face face for clock intervals that are too short" org-clock plist org-agenda-log-mode-add-notes "Non-nil means add first line of notes to log entries in agenda views.\nIf a log item like a state change or a clock entry is associated with\nnotes, the first line of these notes will be added to the entry in the\nagenda display." org-agenda-start-with-log-mode "The initial value of log-mode in a newly created agenda window.\nSee `org-agenda-log-mode' and `org-agenda-log-mode-items' for further\nexplanations on the possible values." org-agenda-startup (choice (const :tag "Don't show log items" nil) (const :tag "Show only log items" only) (const :tag "Show all possible log items" clockcheck) (repeat :tag "Choose among possible values for `org-agenda-log-mode-items'" (choice (const :tag "Show closed log items" closed) (const :tag "Show clocked log items" clock) (const :tag "Show all logged state changes" state)))) org-agenda-start-with-clockreport-mode "The initial value of clockreport-mode in a newly created agenda window." org-agenda-clockreport-parameter-plist '(:link t :maxlevel 2) "Property list with parameters for the clocktable in clockreport mode.\nThis is the display mode that shows a clock table in the daily/weekly\nagenda, the properties for this dynamic block can be set here.\nThe usual clocktable parameters are allowed here, but you cannot set\nthe properties :name, :tstart, :tend, :block, and :scope - these will\nbe overwritten to make sure the content accurately reflects the\ncurrent display in the agenda." org-agenda-search-view-always-boolean "Non-nil means the search string is interpreted as individual parts.\n\nThe search string for search view can either be interpreted as a phrase,\nor as a list of snippets that define a boolean search for a number of\nstrings.\n\nWhen this is non-nil, the string will be split on whitespace, and each\nsnippet will be searched individually, and all must match in order to\nselect an entry. A snippet is then a single string of non-white\ncharacters, or a string in double quotes, or a regexp in {} braces.\nIf a snippet is preceded by \"-\", the snippet must *not* match.\n\"+\" is syntactic sugar for positive selection. Each snippet may\nbe found as a full word or a partial word, but see the variable\n`org-agenda-search-view-force-full-words'.\n\nWhen this is nil, search will look for the entire search phrase as one,\nwith each space character matching any amount of whitespace, including\nline breaks.\n\nEven when this is nil, you can still switch to Boolean search dynamically\nby preceding the first snippet with \"+\" or \"-\". If the first snippet\nis a regexp marked with braces like \"{abc}\", this will also switch to\nboolean search." org-agenda-search-view defvaralias org-agenda-search-view-search-words-only org-agenda-search-view-force-full-words "Non-nil means, search words must be matches as complete words.\nWhen nil, they may also match part of a word." org-agenda-search-view-max-outline-level 0 "Maximum outline level to display in search view.\nE.g. when this is set to 1, the search view will only\nshow headlines of level 1. When set to 0, the default\nvalue, don't limit agenda view by outline level." (Org . "8.3") custom-declare-group org-agenda-time-grid "Options concerning the time grid in the Org Agenda." :tag "Org Agenda Time Grid" org-agenda org-agenda-search-headline-for-time "Non-nil means search headline for a time-of-day.\nIf the headline contains a time-of-day in one format or another, it will\nbe used to sort the entry into the time sequence of items for a day.\nSome people have time stamps in the headline that refer to the creation\ntime or so, and then this produces an unwanted side effect. If this is\nthe case for your, use this variable to turn off searching the headline\nfor a time." org-agenda-use-time-grid "Non-nil means show a time grid in the agenda schedule.\nA time grid is a set of lines for specific times (like every two hours between\n8:00 and 20:00). The items scheduled for a day at specific times are\nsorted in between these lines.\nFor details about when the grid will be shown, and what it will look like, see\nthe variable `org-agenda-time-grid'." '((daily today require-timed) (800 1000 1200 1400 1600 1800 2000) "......" "----------------") "The settings for time grid for agenda display.\nThis is a list of four items. The first item is again a list. It contains\nsymbols specifying conditions when the grid should be displayed:\n\n daily if the agenda shows a single day\n weekly if the agenda shows an entire week\n today show grid on current date, independent of daily/weekly display\n require-timed show grid only if at least one item has a time specification\n remove-match skip grid times already present in an entry\n\nThe second item is a list of integers, indicating the times that\nshould have a grid line.\n\nThe third item is a string which will be placed right after the\ntimes that have a grid line.\n\nThe fourth item is a string placed after the grid times. This\nwill align with agenda items" (list (set :greedy t :tag "Grid Display Options" (const :tag "Show grid in single day agenda display" daily) (const :tag "Show grid in weekly agenda display" weekly) (const :tag "Always show grid for today" today) (const :tag "Show grid only if any timed entries are present" require-timed) (const :tag "Skip grid times already present in an entry" remove-match)) (repeat :tag "Grid Times" (integer :tag "Time")) (string :tag "Grid String (after agenda times)") (string :tag "Grid String (aligns with agenda items)")) org-agenda-show-current-time-in-grid "Non-nil means show the current time in the time grid." org-agenda-current-time-string "now - - - - - - - - - - - - - - - - - - - - - - - - -" "The string for the current time marker in the agenda." string org-agenda-sorting "Options concerning sorting in the Org Agenda." "Org Agenda Sorting" org-agenda-sorting-strategy '((agenda habit-down time-up priority-down category-keep) (todo priority-down category-keep) (tags priority-down category-keep) (search category-keep)) "Sorting structure for the agenda items of a single day.\nThis is a list of symbols which will be used in sequence to determine\nif an entry should be listed before another entry. The following\nsymbols are recognized:\n\ntime-up Put entries with time-of-day indications first, early first\ntime-down Put entries with time-of-day indications first, late first\ntimestamp-up Sort by any timestamp, early first\ntimestamp-down Sort by any timestamp, late first\nscheduled-up Sort by scheduled timestamp, early first\nscheduled-down Sort by scheduled timestamp, late first\ndeadline-up Sort by deadline timestamp, early first\ndeadline-down Sort by deadline timestamp, late first\nts-up Sort by active timestamp, early first\nts-down Sort by active timestamp, late first\ntsia-up Sort by inactive timestamp, early first\ntsia-down Sort by inactive timestamp, late first\ncategory-keep Keep the default order of categories, corresponding to the\n sequence in `org-agenda-files'.\ncategory-up Sort alphabetically by category, A-Z.\ncategory-down Sort alphabetically by category, Z-A.\ntag-up Sort alphabetically by last tag, A-Z.\ntag-down Sort alphabetically by last tag, Z-A.\npriority-up Sort numerically by priority, high priority last.\npriority-down Sort numerically by priority, high priority first.\ntodo-state-up Sort by todo state, tasks that are done last.\ntodo-state-down Sort by todo state, tasks that are done first.\neffort-up Sort numerically by estimated effort, high effort last.\neffort-down Sort numerically by estimated effort, high effort first.\nuser-defined-up Sort according to `org-agenda-cmp-user-defined', high last.\nuser-defined-down Sort according to `org-agenda-cmp-user-defined', high first.\nhabit-up Put entries that are habits first\nhabit-down Put entries that are habits last\nalpha-up Sort headlines alphabetically\nalpha-down Sort headlines alphabetically, reversed\n\nThe different possibilities will be tried in sequence, and testing stops\nif one comparison returns a \"not-equal\". For example, the default\n '(time-up category-keep priority-down)\nmeans: Pull out all entries having a specified time of day and sort them,\nin order to make a time schedule for the current day the first thing in the\nagenda listing for the day. Of the entries without a time indication, keep\nthe grouped in categories, don't sort the categories, but keep them in\nthe sequence given in `org-agenda-files'. Within each category sort by\npriority.\n\nLeaving out `category-keep' would mean that items will be sorted across\ncategories by priority.\n\nInstead of a single list, this can also be a set of list for specific\ncontents, with a context symbol in the car of the list, any of\n`agenda', `todo', `tags', `search' for the corresponding agenda views.\n\nCustom commands can bind this variable in the options section." choice repeat "General" list "Individually" cons (const :tag "Strategy for Weekly/Daily agenda" agenda) (const :tag "Strategy for TODO lists" todo) (const :tag "Strategy for Tags matches" tags) (const :tag "Strategy for search matches" search) org-agenda-cmp-user-defined "A function to define the comparison `user-defined'.\nThis function must receive two arguments, agenda entry a and b.\nIf a>b, return +1. If a<b, return -1. If they are equal as seen by\nthe user comparison, return nil.\nWhen this is defined, you can make `user-defined-up' and `user-defined-down'\npart of an agenda sorting strategy." symbol org-sort-agenda-notime-is-late "Non-nil means items without time are considered late.\nThis is only relevant for sorting. When t, items which have no explicit\ntime like 15:30 will be considered as 99:01, i.e. later than any items which\ndo have a time. When nil, the default time is before 0:00. You can use this\noption to decide if the schedule for today should come before or after timeless\nagenda entries." org-sort-agenda-noeffort-is-high "Non-nil means items without effort estimate are sorted as high effort.\nThis also applies when filtering an agenda view with respect to the\n< or > effort operator. Then, tasks with no effort defined will be treated\nas tasks with high effort.\nWhen nil, such items are sorted as 0 minutes effort." org-agenda-line-format "Options concerning the entry prefix in the Org agenda display." "Org Agenda Line Format" org-agenda-prefix-format '((agenda . " %i %-12:c%?-12t% s") (todo . " %i %-12:c") (tags . " %i %-12:c") (search . " %i %-12:c")) "Format specifications for the prefix of items in the agenda views.\n\nAn alist with one entry per agenda type. The keys of the\nsublists are `agenda', `todo', `search' and `tags'. The values\nare format strings.\n\nThis format works similar to a printf format, with the following meaning:\n\n %c the category of the item, \"Diary\" for entries from the diary,\n or as given by the CATEGORY keyword or derived from the file name\n %e the effort required by the item\n %l the level of the item (insert X space(s) if item is of level X)\n %i the icon category of the item, see `org-agenda-category-icon-alist'\n %T the last tag of the item (ignore inherited tags, which come first)\n %t the HH:MM time-of-day specification if one applies to the entry\n %s Scheduling/Deadline information, a short string\n %b show breadcrumbs, i.e., the names of the higher levels\n %(expression) Eval EXPRESSION and replace the control string\n by the result\n\nAll specifiers work basically like the standard `%s' of printf, but may\ncontain two additional characters: a question mark just after the `%'\nand a whitespace/punctuation character just before the final letter.\n\nIf the first character after `%' is a question mark, the entire field\nwill only be included if the corresponding value applies to the current\nentry. This is useful for fields which should have fixed width when\npresent, but zero width when absent. For example, \"%?-12t\" will\nresult in a 12 character time field if a time of the day is specified,\nbut will completely disappear in entries which do not contain a time.\n\nIf there is punctuation or whitespace character just before the\nfinal format letter, this character will be appended to the field\nvalue if the value is not empty. For example, the format\n\"%-12:c\" leads to \"Diary: \" if the category is \"Diary\". If\nthe category is empty, no additional colon is inserted.\n\nThe default value for the agenda sublist is \" %-12:c%?-12t% s\",\nwhich means:\n\n- Indent the line with two space characters\n- Give the category a 12 chars wide field, padded with whitespace on\n the right (because of `-'). Append a colon if there is a category\n (because of `:').\n- If there is a time-of-day, put it into a 12 chars wide field. If no\n time, don't put in an empty field, just skip it (because of '?').\n- Finally, put the scheduling information.\n\nSee also the variables `org-agenda-remove-times-when-in-prefix' and\n`org-agenda-remove-tags'.\n\nCustom commands can set this variable in the options section." (choice (string :tag "General format") (list :greedy t :tag "View dependent" (cons (const agenda) (string :tag "Format")) (cons (const todo) (string :tag "Format")) (cons (const tags) (string :tag "Format")) (cons (const search) (string :tag "Format")))) (Org . "9.1")] 19) |
|
98 |
#@221 The compiled prefix format and associated variables. |
|
99 |
This is a list where first element is a list of variable bindings, and second |
|
100 |
element is the compiled format expression. See the variable |
|
101 |
`org-agenda-prefix-format'. |
|
102 |
(defvar org-prefix-format-compiled nil (#$ . 64996)) |
|
103 |
(byte-code "\300\301\302\303\304\305\306\307&\210\300\310\311\312\304\305\306\313&\210\300\314\315\316\304\305\306\317&\210\300\320\321\322\304\305\323\324\325\326\306\327&\210\300\330\331\332\304\305\323\333\306\307& \210\300\334\335\336\304\305\323\324\325\337\306\340&\210\300\341\342\343\304\305\306\344&\210\300\345\311\346\304\305\323\333\306\347& \210\300\350\311\351\304\305\306\352&\210\300\353\342\354\304\305\304\355\323\356\306\357&\210\300\360\361\362\304\355\323\363\325\364\306\365&\210\300\366\311\367\304\305\306\370&\210\300\371\311\372\304\305\306\373&\210\374\375\371\"\210\300\376\377\201@ \304\305\306\201A \325\201B \323\363&\210\374\201C \376\"\210\300\201D \201E \201F \304\305\306\201G &\210\300\201H \311\201I \304\305\323\333\306\201J & \210\300\201K \311\201L \304\305\323\333\306\201M & \210\201N \201O \311\201P \201Q \201R \304\355&\210\300\201S \311\201T \304\201O \306\347\323\363\325\201U \201V \201W &
\210\300\201X \342\201Y \304\201O \306\347&\210\300\201Z \342\201[ \304\201O \306\347&\210\300\201\\ \311\201] \304\201O \306\347&\210\300\201^ \311\201_ \304\355\306\201` &\210\300\201a \311\201b \306\201c \323\333\304\355& \207" [custom-declare-variable org-agenda-todo-keyword-format "%-1s" "Format for the TODO keyword in agenda lines.\nSet this to something like \"%-12s\" if you want all TODO keywords\nto occupy a fixed space in the agenda display." :group org-agenda-line-format :type string org-agenda-diary-sexp-prefix nil "A regexp that matches part of a diary sexp entry\nwhich should be treated as scheduling/deadline information in\n`org-agenda'.\n\nFor example, you can use this to extract the `diary-remind-message' from\n`diary-remind' entries." (choice (const :tag "None" nil) (regexp :tag "Regexp")) org-agenda-timerange-leaders '("" "(%d/%d): ") "Text preceding timerange entries in the agenda view.\nThis is a list with two strings. The first applies when the range\nis entirely on one day. The second applies if the range spans several days.\nThe strings may have two \"%d\" format specifiers which will be filled\nwith the sequence number of the days, and the total number of days in the\nrange, respectively." (list (string :tag "Deadline today ") (choice :tag "Deadline relative" (string :tag "Format string") (function))) org-agenda-scheduled-leaders '("Scheduled: " "Sched.%2dx: ") "Text preceding scheduled items in the agenda view.\nThis is a list with two strings. The first applies when the item is\nscheduled on the current day. The second applies when it has been scheduled\npreviously, it may contain a %d indicating that this is the nth time that\nthis item is scheduled, due to automatic rescheduling of unfinished items\nfor the following day. So this number is one larger than the number of days\nthat passed since this item was scheduled first." :version "24.4" :package-version (Org . "8.0") (list (string :tag "Scheduled today ") (string :tag "Scheduled previously")) org-agenda-inactive-leader "[" "Text preceding item pulled into the agenda by inactive time stamps.\nThese entries are added to the agenda when pressing \"[\"." "24.1" org-agenda-deadline-leaders '("Deadline: " "In %3d d.: " "%2d d. ago: ") "Text preceding deadline items in the agenda view.\nThis is a list with three strings. The first applies when the item has its\ndeadline on the current day. The second applies when the deadline is in the\nfuture, the third one when it is in the past. The strings may contain %d\nto capture the number of days." (Org . "8.0") (list (string :tag "Deadline today ") (string :tag "Deadline in the future ") (string :tag "Deadline in the past ")) org-agenda-remove-times-when-in-prefix t "Non-nil means remove duplicate time specifications in agenda items.\nWhen the format `org-agenda-prefix-format' contains a `%t' specifier, a\ntime-of-day specification in a headline or diary entry is extracted and\nplaced into the prefix. If this option is non-nil, the original specification\n(a timestamp or -range, or just a plain time(range) specification like\n11:30-4pm) will be removed for agenda display. This makes the agenda less\ncluttered.\nThe option can be t or nil. It may also be the symbol `beg', indicating\nthat the time should only be removed when it is located at the beginning of\nthe headline/diary entry." (choice (const :tag "Always" t) (const :tag "Never" nil) (const :tag "When at beginning of entry" beg)) org-agenda-remove-timeranges-from-blocks "Non-nil means remove time ranges specifications in agenda\nitems that span on several days." boolean org-agenda-default-appointment-duration "Default duration for appointments that only have a starting time.\nWhen nil, no duration is specified in such cases.\nWhen non-nil, this must be the number of minutes, e.g. 60 for one hour." (choice (integer :tag "Minutes") (const :tag "No default duration")) org-agenda-show-inherited-tags "Non-nil means show inherited tags in each agenda line.\n\nWhen this option is set to `always', it takes precedence over\n`org-agenda-use-tag-inheritance' and inherited tags are shown\nin every agenda.\n\nWhen this option is set to t (the default), inherited tags are\nshown when they are available, i.e. when the value of\n`org-agenda-use-tag-inheritance' enables tag inheritance for the\ngiven agenda type.\n\nThis can be set to a list of agenda types in which the agenda\nmust display the inherited tags. Available types are `todo',\n`agenda' and `search'.\n\nWhen set to nil, never show inherited tags in agenda lines." org-agenda "24.3" (choice (const :tag "Show inherited tags when available" t) (const :tag "Always show inherited tags" always) (repeat :tag "Show inherited tags only in selected agenda types" (symbol :tag "Agenda type"))) org-agenda-use-tag-inheritance '(todo search agenda) "List of agenda view types where to use tag inheritance.\n\nIn tags/tags-todo/tags-tree agenda views, tag inheritance is\ncontrolled by `org-use-tag-inheritance'. In other agenda types,\n`org-use-tag-inheritance' is not used for the selection of the\nagenda entries. Still, you may want the agenda to be aware of\nthe inherited tags anyway, e.g. for later tag filtering.\n\nAllowed value are `todo', `search' and `agenda'.\n\nThis variable has no effect if `org-agenda-show-inherited-tags'\nis set to `always'. In that case, the agenda is aware of those\ntags.\n\nThe default value sets tags in every agenda type. Setting this\noption to nil will speed up non-tags agenda view a lot." "26.1" (Org . "9.1") (choice (const :tag "Use tag inheritance in all agenda types" t) (repeat :tag "Use tag inheritance in selected agenda types" (symbol :tag "Agenda type"))) org-agenda-hide-tags-regexp "Regular expression used to filter away specific tags in agenda views.\nThis means that these tags will be present, but not be shown in the agenda\nline. Secondary filtering will still work on the hidden tags.\nNil means don't hide any tags." (choice (const :tag "Hide none" nil) (string :tag "Regexp ")) org-agenda-remove-tags "Non-nil means remove the tags from the headline copy in the agenda.\nWhen this is the symbol `prefix', only remove tags when\n`org-agenda-prefix-format' contains a `%T' specifier." (choice (const :tag "Always" t) (const :tag "Never" nil) (const :tag "When prefix format contains %T" prefix)) defvaralias org-agenda-remove-tags-when-in-prefix org-agenda-tags-column 'auto "Shift tags in agenda items to this column.\nIf set to `auto', tags will be automatically aligned to the right\nedge of the window.\n\nIf set to a positive number, tags will be left-aligned to that\ncolumn. If set to a negative number, tags will be right-aligned\nto that column. For example, -80 works well for a normal 80\ncharacter screen." (choice (const :tag "Automatically align to right edge of window" auto) (integer :tag "Specific column" -80)) (Org . "9.1") org-agenda-align-tags-to-column org-agenda-fontify-priorities 'cookies "Non-nil means highlight low and high priorities in agenda.\nWhen t, the highest priority entries are bold, lowest priority italic.\nHowever, settings in `org-priority-faces' will overrule these faces.\nWhen this variable is the symbol `cookies', only fontify the\ncookies, not the entire task.\nThis may also be an association list of priority faces, whose\nkeys are the character values of `org-highest-priority',\n`org-default-priority', and `org-lowest-priority' (the default values\nare ?A, ?B, and ?C, respectively). The face may be a named face, a\ncolor as a string, or a list like `(:background \"Red\")'.\nIf it is a color, the variable `org-faces-easy-properties'\ndetermines if it is a foreground or a background color." (choice (const :tag "Never" nil) (const :tag "Defaults" t) (const :tag "Cookies only" cookies) (repeat :tag "Specify" (list (character :tag "Priority" :value 65) (choice :tag "Face " (string :tag "Color") (sexp :tag "Face"))))) org-agenda-day-face-function "Function called to determine what face should be used to display a day.\nThe only argument passed to that function is the day. It should\nreturns a face, or nil if does not want to specify a face and let\nthe normal rules apply." (choice (const nil) (function)) org-agenda-category-icon-alist "Alist of category icon to be displayed in agenda views.\n\nEach entry should have the following format:\n\n (CATEGORY-REGEXP FILE-OR-DATA TYPE DATA-P PROPS)\n\nWhere CATEGORY-REGEXP is a regexp matching the categories where\nthe icon should be displayed.\nFILE-OR-DATA either a file path or a string containing image data.\n\nThe other fields can be omitted safely if not needed:\nTYPE indicates the image type.\nDATA-P is a boolean indicating whether the FILE-OR-DATA string is\nimage data.\nPROPS are additional image attributes to assign to the image,\nlike, e.g. `:ascent center'.\n\n (\"Org\" \"/path/to/icon.png\" nil nil :ascent center)\n\nIf you want to set the display properties yourself, just put a\nlist as second element:\n\n (CATEGORY-REGEXP (MY PROPERTY LIST))\n\nFor example, to display a 16px horizontal space for Emacs\ncategory, you can use:\n\n (\"Emacs\" \\='(space . (:width (16))))" (alist :key-type (string :tag "Regexp matching category") :value-type (choice (list :tag "Icon" (string :tag "File or data") (symbol :tag "Type") (boolean :tag "Data?") (repeat :tag "Extra image properties" :inline t symbol)) (list :tag "Display properties" sexp))) custom-declare-group org-agenda-column-view "Options concerning column view in the agenda." :tag "Org Agenda Column View" org-agenda-view-columns-initially "When non-nil, switch to columns view right after creating the agenda." (Org . "9.0") :safe booleanp org-agenda-columns-show-summaries "Non-nil means show summaries for columns displayed in the agenda view." org-agenda-columns-compute-summary-properties "Non-nil means recompute all summary properties before column view.\nWhen column view in the agenda is listing properties that have a summary\noperator, it can go to all relevant buffers and recompute the summaries\nthere. This can mean overhead for the agenda column view, but is necessary\nto have thing up to date.\nAs a special case, a CLOCKSUM property also makes sure that the clock\ncomputations are current." org-agenda-columns-add-appointments-to-effort-sum "Non-nil means the duration of an appointment will add to day effort.\nThe property to which appointment durations will be added is the one given\nin the option `org-effort-property'. If an appointment does not have\nan end time, `org-agenda-default-appointment-duration' will be used. If that\nis not set, an appointment without end time will not contribute to the time\nestimate." org-agenda-auto-exclude-function "A function called with a tag to decide if it is filtered on \\<org-agenda-mode-map>`\\[org-agenda-filter-by-tag] RET'.\nThe sole argument to the function, which is called once for each\npossible tag, is a string giving the name of the tag. The\nfunction should return either nil if the tag should be included\nas normal, or \"-<TAG>\" to exclude the tag.\nNote that for the purpose of tag filtering, only the lower-case version of\nall tags will be considered, so that this function will only ever see\nthe lower-case version of all tags." (choice (const nil) (function)) org-agenda-bulk-custom-functions "Alist of characters and custom functions for bulk actions.\nFor example, this value makes those two functions available:\n\n \\='((?R set-category)\n (?C bulk-cut))\n\nWith selected entries in an agenda buffer, `B R' will call\nthe custom function `set-category' on the selected entries.\nNote that functions in this alist don't need to be quoted." (alist :key-type character :value-type (group function))] 14) |
|
104 |
#@238 Execute BODY with point at location given by `org-hd-marker' property. |
|
105 |
If STRING is non-nil, the text property will be fetched from position 0 |
|
106 |
in that string. If STRING is nil, it will be fetched from the beginning |
|
107 |
of the current line. |
|
108 |
(defalias 'org-agenda-with-point-at-orig-entry '(macro . #[(string &rest body) "\303\304!\305\306\307 \310BB\311 FDC\312\313D\314\315D\nBBEE)\207" [marker string body make-symbol "--marker" let get-text-property if (0 (point-at-bol)) 'org-hd-marker with-current-buffer marker-buffer save-excursion goto-char] 7 (#$ . 78029)])) |
|
109 |
(put 'org-agenda-with-point-at-orig-entry 'edebug-form-spec '(form body)) |
|
110 |
#@206 Replace or add a command in `org-agenda-custom-commands'. |
|
111 |
This is mostly for hacking and trying a new command - once the command |
|
112 |
works you probably want to add it to `org-agenda-custom-commands' for good. |
|
113 |
(defalias 'org-add-agenda-custom-command #[(entry) "\303@ \"\211\203 \nA\241\202 B\211)\207" [entry org-agenda-custom-commands ass assoc] 4 (#$ . 78678)]) |
|
114 |
#@31 Keymap for `org-agenda-mode'. |
|
115 |
(defvar org-agenda-mode-map (make-sparse-keymap) (#$ . 79052)) |
|
116 |
(defvaralias 'org-agenda-keymap 'org-agenda-mode-map) |
|
117 |
(defvar org-agenda-restrict nil) |
|
118 |
(defvar org-agenda-follow-mode nil) |
|
119 |
(defvar org-agenda-entry-text-mode nil) |
|
120 |
(defvar org-agenda-clockreport-mode nil) |
|
121 |
#@126 When non-nil, show the log in the agenda. |
|
122 |
Do not set this directly; instead use |
|
123 |
`org-agenda-start-with-log-mode', which see. |
|
124 |
(defvar org-agenda-show-log nil (#$ . 79356)) |
|
125 |
(defvar org-agenda-redo-command nil) |
|
126 |
(defvar org-agenda-query-string nil) |
|
127 |
#@103 Hook run after `org-agenda-mode' is turned on. |
|
128 |
The buffer is still writable when this hook is called. |
|
129 |
(defvar org-agenda-mode-hook nil (#$ . 79608)) |
|
130 |
(defvar org-agenda-type nil) |
|
131 |
(defvar org-agenda-force-single-file nil) |
|
132 |
#@61 List of markers that refer to marked entries in the agenda. |
|
133 |
(defvar org-agenda-bulk-marked-entries nil (#$ . 79834)) |
|
134 |
#@39 Active date when building the agenda. |
|
135 |
(defvar org-agenda-current-date nil (#$ . 79957)) |
|
136 |
#@183 Non-nil means agenda q key will bury agenda buffers. |
|
137 |
Agenda commands will then show existing buffer instead of generating new ones. |
|
138 |
When nil, `q' will kill the single agenda buffer. |
|
139 |
(custom-declare-variable 'org-agenda-sticky nil '(#$ . 80052) :group 'org-agenda :version "24.3" :type 'boolean) |
|
140 |
#@29 Toggle `org-agenda-sticky'. |
|
141 |
(defalias 'org-toggle-sticky-agenda #[(&optional arg) "\203\f \303!\304V\202 ?\211 \232\203* \305\306!\205A \307\310 \203% \311\202& |