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.elc
;ELC ;;; Compiled by mockbuild@c6b8.bsys.dev.centos.org on Thu Feb 19 13:04:54 2015 ;;; from file /builddir/build/BUILD/emacs-23.1/lisp/org/org.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.el' was compiled for Emacs 19.29 or later")) ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; (byte-code "\301B\302\301!\204 \303\301\304\"\210\304\207" [current-load-list org-inhibit-highlight-removal default-boundp set-default nil] 3) #@49 Local version of `org-table-formula-constants'. (defvar org-table-formula-constants-local nil (#$ . 747)) (byte-code "\300\301!\210\302\303!\210\302\304!\210\302\305!\210\306\307!\204 \310\307\311\"\210\302\312!\210\302\313!\210\302\314!\210\302\315!\210\302\316!\210\302\317!\207" [make-variable-buffer-local org-table-formula-constants-local require outline noutline time-date fboundp time-subtract defalias subtract-time easymenu org-macs org-compat org-faces org-list org-footnote] 3) #@40 The version number of the file org.el. (defconst org-version "6.21b" (#$ . 1243)) #@87 Show the org-mode version in the echo area. With prefix arg HERE, insert it at point. (defalias 'org-version #[(&optional here) "\303\304\"\305 !\210\n\205 c)\207" [org-version version here format "Org-mode version %s" message] 3 (#$ . 1331) "P"]) (custom-declare-group 'org nil "Outline-based notes management and organizer." :tag "Org" :group 'outlines :group 'hypermedia :group 'calendar) #@48 Hook that is run after org.el has been loaded. (custom-declare-variable 'org-load-hook 'nil '(#$ . 1733) :group 'org :type 'hook) #@39 Have the modules been loaded already? (defvar org-modules-loaded nil (#$ . 1869)) #@46 Load all extensions listed in `org-modules'. (defalias 'org-load-modules-maybe #[(&optional force) "\204 ?\205 \303\304\n\"\210\305\211\207" [force org-modules-loaded org-modules mapc #[(ext) "\300\301\302\217\207" [nil (require ext) ((error (message "Problems while trying to load feature `%s'" ext)))] 3] t] 3 (#$ . 1957)]) #@73 Set VAR to VALUE and call `org-load-modules-maybe' with the force flag. (defalias 'org-set-modules #[(var value) " L\210\302\303!\205 \304\305!\207" [var value featurep org org-load-modules-maybe force] 2 (#$ . 2294)]) (byte-code "\302\300!\203 \203 \303\235\211\203 \304\240\210)\302\207" [org-modules a boundp org-infojs org-jsinfo] 3) #@534 Modules that should always be loaded together with org.el. If a description starts with <C>, the file is not part of Emacs and loading it will require that you have downloaded and properly installed the org-mode distribution. You can also use this system to load external packages (i.e. neither Org core modules, not modules from the CONTRIB directory). Just add symbols to the end of the list. If the package is called org-xyz.el, then you need to add the symbol `xyz', and the package must have a call to (provide 'org-xyz) (custom-declare-variable 'org-modules ''(org-bbdb org-bibtex org-gnus org-info org-jsinfo org-irc org-mew org-mhe org-rmail org-vm org-w3m org-wl) '(#$ . 2648) :group 'org :set 'org-set-modules :type '(set :greedy t (const :tag " bbdb: Links to BBDB entries" org-bbdb) (const :tag " bibtex: Links to BibTeX entries" org-bibtex) (const :tag " gnus: Links to GNUS folders/messages" org-gnus) (const :tag " id: Global IDs for identifying entries" org-id) (const :tag " info: Links to Info nodes" org-info) (const :tag " jsinfo: Set up Sebastian Rose's JavaScript org-info.js" org-jsinfo) (const :tag " irc: Links to IRC/ERC chat sessions" org-irc) (const :tag " mac-message: Links to messages in Apple Mail" org-mac-message) (const :tag " mew Links to Mew folders/messages" org-mew) (const :tag " mhe: Links to MHE folders/messages" org-mhe) (const :tag " rmail: Links to RMAIL folders/messages" org-rmail) (const :tag " vm: Links to VM folders/messages" org-vm) (const :tag " wl: Links to Wanderlust folders/messages" org-wl) (const :tag " w3m: Special cut/past from w3m to Org." org-w3m) (const :tag " mouse: Additional mouse support" org-mouse) (const :tag "C annotate-file: Annotate a file with org syntax" org-annotate-file) (const :tag "C annotation-helper: Call Remember directly from Browser" org-annotation-helper) (const :tag "C bookmark: Org links to bookmarks" org-bookmark) (const :tag "C browser-url: Store link, directly from Browser" org-browser-url) (const :tag "C depend: TODO dependencies for Org-mode" org-depend) (const :tag "C elisp-symbol: Org links to emacs-lisp symbols" org-elisp-symbol) (const :tag "C eval: Include command output as text" org-eval) (const :tag "C eval-light: Evaluate inbuffer-code on demand" org-eval-light) (const :tag "C expiry: Expiry mechanism for Org entries" org-expiry) (const :tag "C exp-blocks: Pre-process blocks for export" org-exp-blocks) (const :tag "C interactive-query: Interactive modification of tags query" org-interactive-query) (const :tag "C mairix: Hook mairix search into Org for different MUAs" org-mairix) (const :tag "C man: Support for links to manpages in Org-mode" org-man) (const :tag "C mtags: Support for muse-like tags" org-mtags) (const :tag "C panel: Simple routines for us with bad memory" org-panel) (const :tag "C registry: A registry for Org links" org-registry) (const :tag "C org2rem: Convert org appointments into reminders" org2rem) (const :tag "C screen: Visit screen sessions through Org-mode links" org-screen) (const :tag "C toc: Table of contents for Org-mode buffer" org-toc) (const :tag "C sqlinsert: Convert Org-mode tables to SQL insertions" orgtbl-sqlinsert) (repeat :tag "External packages" :inline t (symbol :tag "Package")))) #@1927 Non-nil means, make shift-cursor commands select text when possible. In Emacs 23, when `shift-select-mode' is on, shifted cursor keys start selecting a region, or enlarge thusly regions started in this way. In Org-mode, in special contexts, these same keys are used for other purposes, important enough to compete with shift selection. Org tries to balance these needs by supporting `shift-select-mode' outside these special contexts, under control of this variable. The default of this variable is nil, to avoid confusing behavior. Shifted cursor keys will then execute Org commands in the following contexts: - on a headline, changing TODO state (left/right) and priority (up/down) - on a time stamp, changing the time - in a plain list item, changing the bullet type - in a property definition line, switching between allowed values - in the BEGIN line of a clock table (changing the time block). Outside these contexts, the commands will throw an error. When this variable is t and the cursor is not in a special context, Org-mode will support shift-selection for making and enlarging regions. To make this more effective, the bullet cycling will no longer happen anywhere in an item line, but only if the cursor is exactly on the bullet. If you set this variable to the symbol `always', then the keys will not be special in headlines, property lines, and item lines, to make shift selection work there as well. If this is what you want, you can use the following alternative commands: `C-c C-t' and `C-c ,' to change TODO state and priority, `C-u C-u C-c C-t' can be used to switch TODO sets, `C-c -' to cycle item bullet types, and properties can be edited by hand or in column view. However, when the cursor is on a timestamp, shift-cursor commands will still edit the time stamp - this is just too good to give up. XEmacs user should have this variable set to nil, because shift-select-mode is Emacs 23 only. (custom-declare-variable 'org-support-shift-select 'nil '(#$ . 6331) :group 'org :type '(choice (const :tag "Never" nil) (const :tag "When outside special context" t) (const :tag "Everywhere except timestamps" always))) (custom-declare-group 'org-startup nil "Options concerning startup of Org-mode." :tag "Org Startup" :group 'org) #@231 Non-nil means, entering Org-mode will switch to OVERVIEW. This can also be configured on a per-file basis by adding one of the following lines anywhere in the buffer: #+STARTUP: fold #+STARTUP: nofold #+STARTUP: content (custom-declare-variable 'org-startup-folded 't '(#$ . 8597) :group 'org-startup :type '(choice (const :tag "nofold: show all" nil) (const :tag "fold: overview" t) (const :tag "content: all headlines" content))) #@187 Non-nil means, entering Org-mode will set `truncate-lines'. This is useful since some lines containing links can be very long and uninteresting. Also tables look terrible when wrapped. (custom-declare-variable 'org-startup-truncated 't '(#$ . 9046) :group 'org-startup :type 'boolean) #@359 Non-nil means, align all tables when visiting a file. This is useful when the column width in tables is forced with <N> cookies in table fields. Such tables will look correct only after the first re-align. This can also be configured on a per-file basis by adding one of the following lines anywhere in the buffer: #+STARTUP: align #+STARTUP: noalign (custom-declare-variable 'org-startup-align-all-tables 'nil '(#$ . 9339) :group 'org-startup :type 'boolean) #@376 Non-nil means insert the first line setting Org-mode in empty files. When the function `org-mode' is called interactively in an empty file, this normally means that the file name does not automatically trigger Org-mode. To ensure that the file will always be in Org-mode in the future, a line enforcing Org-mode will be inserted into the buffer, if this option has been set. (custom-declare-variable 'org-insert-mode-line-in-empty-file 'nil '(#$ . 9813) :group 'org-startup :type 'boolean) #@597 Non-nil means use alternative key bindings for some keys. Org-mode uses S-<cursor> keys for changing timestamps and priorities. These keys are also used by other packages like `CUA-mode' or `windmove.el'. If you want to use Org-mode together with one of these other modes, or more generally if you would like to move some Org-mode commands to other keys, set this variable and configure the keys with the variable `org-disputed-keys'. This option is only relevant at load-time of Org-mode, and must be set *before* org.el is loaded. Changing it requires a restart of Emacs to become effective. (custom-declare-variable 'org-replace-disputed-keys 'nil '(#$ . 10310) :group 'org-startup :type 'boolean) #@443 Non-nil means use extra key sequence definitions for certain commands. This happens automatically if you run XEmacs or if window-system is nil. This variable lets you do the same manually. You must set it before loading org. Example: on Carbon Emacs 22 running graphically, with an external keyboard on a Powerbook, the default way of setting M-left might not work for either Alt or ESC. Setting this variable will make it work for ESC. (custom-declare-variable 'org-use-extra-keys 'nil '(#$ . 11020) :group 'org-startup :type 'boolean) (byte-code "\300\301!\203 \301\302\303\"\210\300\207" [fboundp defvaralias org-CUA-compatible org-replace-disputed-keys] 3) #@379 Keys for which Org-mode and other modes compete. This is an alist, cars are the default keys, second element specifies the alternative to use when `org-replace-disputed-keys' is t. Keys can be specified in any syntax supported by `define-key'. The value of this option takes effect only at Org-mode's startup, therefore you'll have to restart Emacs to apply it after changing. (custom-declare-variable 'org-disputed-keys ''(([(shift up)] . [(meta p)]) ([(shift down)] . [(meta n)]) ([(shift left)] . [(meta -)]) ([(shift right)] . [(meta +)]) ([(control shift right)] . [(meta shift +)]) ([(control shift left)] . [(meta shift -)])) '(#$ . 11694) :group 'org-startup :type 'alist) #@118 Select key according to `org-replace-disputed-keys' and `org-disputed-keys'. Or return the original if not disputed. (defalias 'org-key #[(key) "\203 \305 !\306\307\"\211\203 \fA\202 *\207 \207" [org-replace-disputed-keys key nkey org-disputed-keys x key-description org-find-if #[(x) "\302@! \232\207" [x nkey key-description] 2]] 4 (#$ . 12383)]) (defalias 'org-find-if #[(predicate seq) "\300\301\215\207" [exit (byte-code "\205 @!\203 \302\303@\"\210\202 \211A@\210\202 \207" [seq predicate throw exit] 3)] 2]) #@62 Define a key, possibly translated, as returned by `org-key'. (defalias 'org-defkey #[(keymap key def) "\303\304 !\n#\207" [keymap key def define-key org-key] 4 (#$ . 12923)]) #@350 The ellipsis to use in the Org-mode outline. When nil, just use the standard three dots. When a string, use that instead, When a face, use the standard 3 dots, but with the specified face. The change affects only Org-mode (which will then use its own display table). Changing this requires executing `M-x org-mode' in a buffer to become effective. (custom-declare-variable 'org-ellipsis 'nil '(#$ . 13106) :group 'org-startup :type '(choice (const :tag "Default" nil) (face :tag "Face" :value org-warning) (string :tag "String" :value "...#"))) #@68 The display table for org-mode, in case `org-ellipsis' is non-nil. (defvar org-display-table nil (#$ . 13658)) (custom-declare-group 'org-keywords nil "Keywords in Org-mode." :tag "Org Keywords" :group 'org) #@256 String to mark deadline entries. A deadline is this string, followed by a time stamp. Should be a word, terminated by a colon. You can insert a schedule keyword and a timestamp with \[org-deadline]. Changes become only effective after restarting Emacs. (custom-declare-variable 'org-deadline-string '"DEADLINE:" '(#$ . 13873) :group 'org-keywords :type 'string) #@262 String to mark scheduled TODO entries. A schedule is this string, followed by a time stamp. Should be a word, terminated by a colon. You can insert a schedule keyword and a timestamp with \[org-schedule]. Changes become only effective after restarting Emacs. (custom-declare-variable 'org-scheduled-string '"SCHEDULED:" '(#$ . 14244) :group 'org-keywords :type 'string) #@72 String used as the prefix for timestamps logging closing a TODO entry. (custom-declare-variable 'org-closed-string '"CLOSED:" '(#$ . 14622) :group 'org-keywords :type 'string) #@70 String used as prefix for timestamps clocking work hours on an item. (custom-declare-variable 'org-clock-string '"CLOCK:" '(#$ . 14804) :group 'org-keywords :type 'string) #@193 Entries starting with this keyword will never be exported. An entry can be toggled between COMMENT and normal with \[org-toggle-comment]. Changes become only effective after restarting Emacs. (custom-declare-variable 'org-comment-string '"COMMENT" '(#$ . 14983) :group 'org-keywords :type 'string) #@308 Entries starting with this keyword will be exported in fixed-width font. Quoting applies only to the text in the entry following the headline, and does not extend beyond the next headline, even if that is lower level. An entry can be toggled between QUOTE and normal with \[org-toggle-fixed-width-section]. (custom-declare-variable 'org-quote-string '"QUOTE" '(#$ . 15288) :group 'org-keywords :type 'string) #@107 Regular expression for specifying repeated events. After a match, group 1 contains the repeat expression. (defconst org-repeat-re "<[0-9]\\{4\\}-[0-9][0-9]-[0-9][0-9] [^>\n]*\\([.+]?\\+[0-9]+[dwmy]\\)" (#$ . 15704)) (byte-code "\300\301\302\303\304\305\306\307&\210\300\310\302\311\304\312\306\301&\207" [custom-declare-group org-structure nil "Options concerning the general structure of Org-mode files." :tag "Org Structure" :group org org-reveal-location "Options about how to make context of a location visible." "Org Reveal Location"] 8) #@34 Contexts for the reveal options. (defconst org-context-choice '(choice (const :tag "Always" t) (const :tag "Never" nil) (repeat :greedy t :tag "Individual contexts" (cons (choice :tag "Context" (const agenda) (const org-goto) (const occur-tree) (const tags-tree) (const link-search) (const mark-goto) (const bookmark-jump) (const isearch) (const default)) (boolean)))) (#$ . 16255)) #@965 Non-nil means, show full hierarchy when revealing a location. Org-mode often shows locations in an org-mode file which might have been invisible before. When this is set, the hierarchy of headings above the exposed location is shown. Turning this off for example for sparse trees makes them very compact. Instead of t, this can also be an alist specifying this option for different contexts. Valid contexts are agenda when exposing an entry from the agenda org-goto when using the command `org-goto' on key C-c C-j occur-tree when using the command `org-occur' on key C-c / tags-tree when constructing a sparse tree based on tags matches link-search when exposing search matches associated with a link mark-goto when exposing the jump goal of a mark bookmark-jump when exposing a bookmark location isearch when exiting from an incremental search default default for all contexts not set explicitly (custom-declare-variable 'org-show-hierarchy-above ''((default . t)) '(#$ . 16645) :group 'org-reveal-location :type org-context-choice) #@552 Non-nil means, show following heading when revealing a location. Org-mode often shows locations in an org-mode file which might have been invisible before. When this is set, the heading following the match is shown. Turning this off for example for sparse trees makes them very compact, but makes it harder to edit the location of the match. In such a case, use the command \[org-reveal] to show more context. Instead of t, this can also be an alist specifying this option for different contexts. See `org-show-hierarchy-above' for valid contexts. (custom-declare-variable 'org-show-following-heading ''((default)) '(#$ . 17753) :group 'org-reveal-location :type org-context-choice) #@761 Non-nil means, show all sibling heading when revealing a location. Org-mode often shows locations in an org-mode file which might have been invisible before. When this is set, the sibling of the current entry heading are all made visible. If `org-show-hierarchy-above' is t, the same happens on each level of the hierarchy above the current entry. By default this is on for the isearch context, off for all other contexts. Turning this off for example for sparse trees makes them very compact, but makes it harder to edit the location of the match. In such a case, use the command \[org-reveal] to show more context. Instead of t, this can also be an alist specifying this option for different contexts. See `org-show-hierarchy-above' for valid contexts. (custom-declare-variable 'org-show-siblings ''((default) (isearch t)) '(#$ . 18446) :group 'org-reveal-location :type org-context-choice) #@425 Non-nil means, show the entry below a headline when revealing a location. Org-mode often shows locations in an org-mode file which might have been invisible before. When this is set, the text below the headline that is exposed is also shown. By default this is off for all contexts. Instead of t, this can also be an alist specifying this option for different contexts. See `org-show-hierarchy-above' for valid contexts. (custom-declare-variable 'org-show-entry-below ''((default)) '(#$ . 19351) :group 'org-reveal-location :type org-context-choice) #@550 How should indirect tree buffers be displayed? This applies to indirect buffers created with the commands \[org-tree-to-indirect-buffer] and \[org-agenda-tree-to-indirect-buffer]. Valid values are: current-window Display in the current window other-window Just display in another window. dedicated-frame Create one new frame, and re-use it each time. new-frame Make a new frame each time. Note that in this case previously-made indirect buffers are kept, and you need to kill these buffers yourself. (custom-declare-variable 'org-indirect-buffer-display ''other-window '(#$ . 19911) :group 'org-structure :group 'org-agenda-windows :type '(choice (const :tag "In current window" current-window) (const :tag "In current frame, other window" other-window) (const :tag "Each time a new frame" new-frame) (const :tag "One dedicated frame" dedicated-frame))) (custom-declare-group 'org-cycle nil "Options concerning visibility cycling in Org-mode." :tag "Org Cycle" :group 'org-structure) #@380 Names of drawers. Drawers are not opened by cycling on the headline above. Drawers only open with a TAB on the drawer line itself. A drawer looks like this: :DRAWERNAME: ..... :END: The drawer "PROPERTIES" is special for capturing properties through the property API. Drawers can be defined on the per-file basis with a line like: #+DRAWERS: HIDDEN STATE PROPERTIES (custom-declare-variable 'org-drawers ''("PROPERTIES" "CLOCK") '(#$ . 20951) :group 'org-structure :type '(repeat (string :tag "Drawer Name"))) #@492 Cycle globally if cursor is at beginning of buffer and not at a headline. This makes it possible to do global cycling without having to use S-TAB or C-u TAB. For this special case to work, the first line of the buffer must not be a headline - it may be empty or some other text. When used in this way, `org-cycle-hook' is disables temporarily, to make sure the cursor stays at the beginning of the buffer. When this option is nil, don't do anything special at the beginning of the buffer. (custom-declare-variable 'org-cycle-global-at-bob 'nil '(#$ . 21481) :group 'org-cycle :type 'boolean) #@375 Where should `org-cycle' emulate TAB. nil Never white Only in completely white lines whitestart Only at the beginning of lines, before the first non-white char t Everywhere except in headlines exc-hl-bol Everywhere except at the start of a headline If TAB is used in a place where it does not emulate TAB, the current subtree visibility is cycled. (custom-declare-variable 'org-cycle-emulate-tab 't '(#$ . 22082) :group 'org-cycle :type '(choice (const :tag "Never" nil) (const :tag "Only in completely white lines" white) (const :tag "Before first char in a line" whitestart) (const :tag "Everywhere except in headlines" t) (const :tag "Everywhere except at bol in headlines" exc-hl-bol))) #@583 Number of empty lines needed to keep an empty line between collapsed trees. If you leave an empty line between the end of a subtree and the following headline, this empty line is hidden when the subtree is folded. Org-mode will leave (exactly) one empty line visible if the number of empty lines is equal or larger to the number given in this variable. So the default 2 means, at least 2 empty lines after the end of a subtree are needed to produce free space between a collapsed subtree and the following headline. Special case: when 0, never leave empty lines in collapsed view. (custom-declare-variable 'org-cycle-separator-lines '2 '(#$ . 22806) :group 'org-cycle :type 'integer) (put 'org-cycle-separator-lines 'safe-local-variable 'integerp) #@414 Hook that is run after `org-cycle' has changed the buffer visibility. The function(s) in this hook must accept a single argument which indicates the new state that was set by the most recent `org-cycle' command. The argument is a symbol. After a global state change, it can have the values `overview', `content', or `all'. After a local state change, it can have the values `folded', `children', or `subtree'. (custom-declare-variable 'org-cycle-hook ''(org-cycle-hide-archived-subtrees org-cycle-hide-drawers org-cycle-show-empty-lines org-optimize-window-after-visibility-change) '(#$ . 23562) :group 'org-cycle :type 'hook) (custom-declare-group 'org-edit-structure nil "Options concerning structure editing in Org-mode." :tag "Org Edit Structure" :group 'org-structure) #@486 Non-nil means, skip even levels and only use odd levels for the outline. This has the effect that two stars are being added/taken away in promotion/demotion commands. It also influences how levels are handled by the exporters. Changing it requires restart of `font-lock-mode' to become effective for fontification also in regions already fontified. You may also set this on a per-file basis by adding one of the following lines to the buffer: #+STARTUP: odd #+STARTUP: oddeven (custom-declare-variable 'org-odd-levels-only 'nil '(#$ . 24346) :group 'org-edit-structure :group 'org-font-lock :type 'boolean) #@323 Non-nil means, adapt indentation when promoting and demoting. When this is set and the *entire* text in an entry is indented, the indentation is increased by one space in a demotion command, and decreased by one in a promotion command. If any line in the entry body starts at column 0, indentation is not changed at all. (custom-declare-variable 'org-adapt-indentation 't '(#$ . 24968) :group 'org-edit-structure :type 'boolean) #@708 Non-nil means `C-a' and `C-e' behave specially in headlines and items. When t, `C-a' will bring back the cursor to the beginning of the headline text, i.e. after the stars and after a possible TODO keyword. In an item, this will be the position after the bullet. When the cursor is already at that position, another `C-a' will bring it to the beginning of the line. `C-e' will jump to the end of the headline, ignoring the presence of tags in the headline. A second `C-e' will then jump to the true end of the line, after any tags. When set to the symbol `reversed', the first `C-a' or `C-e' works normally, and only a directly following, identical keypress will bring the cursor to the special positions. (custom-declare-variable 'org-special-ctrl-a/e 'nil '(#$ . 25405) :group 'org-edit-structure :type '(choice (const :tag "off" nil) (const :tag "after bullet first" t) (const :tag "border first" reversed))) (byte-code "\300\301!\203 \301\302\303\"\210\300\207" [fboundp defvaralias org-special-ctrl-a org-special-ctrl-a/e] 3) #@436 Non-nil means `C-k' will behave specially in headlines. When nil, `C-k' will call the default `kill-line' command. When t, the following will happen while the cursor is in the headline: - When the cursor is at the beginning of a headline, kill the entire line and possible the folded subtree below the line. - When in the middle of the headline text, kill the headline up to the tags. - When after the headline text, kill the tags. (custom-declare-variable 'org-special-ctrl-k 'nil '(#$ . 26445) :group 'org-edit-structure :type 'boolean) #@336 Non-nil means, when yanking subtrees, fold them. If the kill is a single subtree, or a sequence of subtrees, i.e. if it starts with a heading and all other headings in it are either children or siblings, then fold all the subtrees. However, do this only if no text after the yank would be swallowed into a folded tree by this action. (custom-declare-variable 'org-yank-folded-subtrees 't '(#$ . 26994) :group 'org-edit-structure :type 'boolean) #@158 Non-nil means, when yanking subtrees, adjust the level. With this setting, `org-paste-subtree' is used to insert the subtree, see this function for details. (custom-declare-variable 'org-yank-adjusted-subtrees 'nil '(#$ . 27447) :group 'org-edit-structure :type 'boolean) #@415 Non-nil means, M-RET will split the line at the cursor position. When nil, it will go to the end of the line before making a new line. You may also set this option in a different way for different contexts. Valid contexts are: headline when creating a new headline item when creating a new item table in a table field default the value to be used for all contexts not explicitly customized (custom-declare-variable 'org-M-RET-may-split-line ''((default . t)) '(#$ . 27726) :group 'org-structure :group 'org-table :type '(choice (const :tag "Always" t) (const :tag "Never" nil) (repeat :greedy t :tag "Individual contexts" (cons (choice :tag "Context" (const headline) (const item) (const table) (const default)) (boolean))))) #@286 Non-nil means, insert new headings after the current subtree. When nil, the new heading is created directly after the current line. The commands \[org-insert-heading-respect-content] and \[org-insert-todo-heading-respect-content] turn this variable on for the duration of the command. (custom-declare-variable 'org-insert-heading-respect-content 'nil '(#$ . 28483) :group 'org-structure :type 'boolean) #@168 Should `org-insert-heading' leave a blank line before new heading/item? The value is an alist, with `heading' and `plain-list-item' as car, and a boolean flag as cdr. (custom-declare-variable 'org-blank-before-new-entry ''((heading . auto) (plain-list-item . auto)) '(#$ . 28893) :group 'org-edit-structure :type '(list (cons (const heading) (choice (const :tag "Never" nil) (const :tag "Always" t) (const :tag "Auto" auto))) (cons (const plain-list-item) (choice (const :tag "Never" nil) (const :tag "Always" t) (const :tag "Auto" auto))))) #@47 Hook being run after inserting a new heading. (custom-declare-variable 'org-insert-heading-hook 'nil '(#$ . 29441) :group 'org-edit-structure :type 'hook) #@210 Non-nil means, lines starting with ":" are treated as fixed-width. This currently only means, they are never auto-wrapped. When nil, such lines will be treated like ordinary lines. See also the QUOTE keyword. (custom-declare-variable 'org-enable-fixed-width-editor 't '(#$ . 29603) :group 'org-edit-structure :type 'boolean) #@346 Additional regexps to identify regions for editing with `org-edit-src-code'. For examples see the function `org-edit-src-find-region-and-lang'. The regular expression identifying the begin marker should end with a newline, and the regexp marking the end line should start with a newline, to make sure there are kept outside the narrowed region. (custom-declare-variable 'org-edit-src-region-extra 'nil '(#$ . 29935) :group 'org-edit-structure :type '(repeat (list (regexp :tag "begin regexp") (regexp :tag "end regexp") (choice :tag "language" (string :tag "specify") (integer :tag "from match group") (const :tag "from `lang' element") (const :tag "from `style' element"))))) #@546 The default coderef format. This format string will be used to search for coderef labels in literal examples (EXAMPLE and SRC blocks). The format can be overwritten an individual literal example with the -f option, like #+BEGIN_SRC pascal +n -r -l "((%s))" ... #+END_SRC If you want to use this for HTML export, make sure that the format does not introduce special font-locking, and avoid the HTML special characters `<', `>', and `&'. The reason for this restriction is that the labels are searched for only after htmlize has done its job. (custom-declare-variable 'org-coderef-label-format '"(ref:%s)" '(#$ . 30619) :group 'org-edit-structure :type 'string) #@118 The mode that should be used to edit fixed-width regions. These are the regions where each line starts with a colon. (custom-declare-variable 'org-edit-fixed-width-region-mode ''artist-mode '(#$ . 31290) :group 'org-edit-structure :type '(choice (const artist-mode) (const picture-mode) (const fundamental-mode) (function :tag "Other (specify)"))) #@73 Non-nil means, typing characters in org-goto starts incremental search. (custom-declare-variable 'org-goto-auto-isearch 't '(#$ . 31644) :group 'org-edit-structure :type 'boolean) (custom-declare-group 'org-sparse-trees nil "Options concerning sparse trees in Org-mode." :tag "Org Sparse Trees" :group 'org-structure) #@165 Non-nil means, highlight all matches that define a sparse tree. The highlights will automatically disappear the next time the buffer is changed by an edit command. (custom-declare-variable 'org-highlight-sparse-tree-matches 't '(#$ . 31969) :group 'org-sparse-trees :type 'boolean) #@301 Non-nil means, any change to the buffer will remove temporary highlights. Such highlights are created by `org-occur' and `org-clock-display'. When nil, `C-c C-c needs to be used to get rid of the highlights. The highlights created by `org-preview-latex-fragment' always need `C-c C-c' to be removed. (custom-declare-variable 'org-remove-highlights-with-change 't '(#$ . 32258) :group 'org-sparse-trees :group 'org-time :type 'boolean) #@153 Hook that is run after `org-occur' has constructed a sparse tree. This can be used to recenter the window to show as much of the structure as possible. (custom-declare-variable 'org-occur-hook ''(org-first-headline-recenter) '(#$ . 32700) :group 'org-sparse-trees :type 'hook) (custom-declare-group 'org-imenu-and-speedbar nil "Options concerning imenu and speedbar in Org-mode." :tag "Org Imenu and Speedbar" :group 'org-structure) #@98 The maximum level for Imenu access to Org-mode headlines. This also applied for speedbar access. (custom-declare-variable 'org-imenu-depth '2 '(#$ . 33139) :group 'org-imenu-and-speedbar :type 'number) (custom-declare-group 'org-table nil "Options concerning tables in Org-mode." :tag "Org Table" :group 'org) #@1301 Non-nil means, lines starting with "|" are handled by the table editor. When nil, such lines will be treated like ordinary lines. When equal to the symbol `optimized', the table editor will be optimized to do the following: - Automatic overwrite mode in front of whitespace in table fields. This makes the structure of the table stay in tact as long as the edited field does not exceed the column width. - Minimize the number of realigns. Normally, the table is aligned each time TAB or RET are pressed to move to another field. With optimization this happens only if changes to a field might have changed the column width. Optimization requires replacing the functions `self-insert-command', `delete-char', and `backward-delete-char' in Org-mode buffers, with a slight (in fact: unnoticeable) speed impact for normal typing. Org-mode is very good at guessing when a re-align will be necessary, but you can always force one with \[org-ctrl-c-ctrl-c]. If you would like to use the optimized version in Org-mode, but the un-optimized version in OrgTbl-mode, see the variable `orgtbl-optimized'. This variable can be used to turn on and off the table editor during a session, but in order to toggle optimization, a restart is required. See also the variable `org-table-auto-blank-field'. (custom-declare-variable 'org-enable-table-editor ''optimized '(#$ . 33457) :group 'org-table :type '(choice (const :tag "off" nil) (const :tag "on" t) (const :tag "on, optimized" optimized))) #@166 Non-nil means, TAB will automatically notice a table.el table. When it sees such a table, it moves point into it and - if necessary - calls `table-recognize-table'. (custom-declare-variable 'org-table-tab-recognizes-table\.el 't '(#$ . 34957) :group 'org-table-editing :type 'boolean) (custom-declare-group 'org-link nil "Options concerning links in Org-mode." :tag "Org Link" :group 'org) #@111 Buffer-local version of `org-link-abbrev-alist', which see. The value of this is taken from the #+LINK lines. (defvar org-link-abbrev-alist-local nil (#$ . 35354)) (make-variable-buffer-local 'org-link-abbrev-alist-local) #@755 Alist of link abbreviations. The car of each element is a string, to be replaced at the start of a link. The cdrs are replacement values, like ("linkkey" . REPLACE). Abbreviated links in Org-mode buffers can have an optional tag after a double colon, e.g. [[linkkey:tag][description]] If REPLACE is a string, the tag will simply be appended to create the link. If the string contains "%s", the tag will be inserted there. Alternatively, the placeholder "%h" will cause a url-encoded version of the tag to be inserted at that point (see the function `url-hexify-string'). REPLACE may also be a function that will be called with the tag as the only argument to create the link, which should be returned as a string. See the manual for examples. (custom-declare-variable 'org-link-abbrev-alist 'nil '(#$ . 35583) :group 'org-link :type '(repeat (cons (string :tag "Protocol") (choice (string :tag "Format") (function))))) #@270 Non-nil means, hide link part and only show description of bracket links. Bracket links are like [[link][description]]. This variable sets the initial state in new org-mode buffers. The setting can then be toggled on a per-buffer basis from the Org->Hyperlinks menu. (custom-declare-variable 'org-descriptive-links 't '(#$ . 36520) :group 'org-link :type 'boolean) #@460 How the path name in file links should be stored. Valid values are: relative Relative to the current directory, i.e. the directory of the file into which the link is being inserted. absolute Absolute path, if possible with ~ for home directory. noabbrev Absolute path, no abbreviation of home directory. adaptive Use relative path for files in the current directory and sub- directories of it. For other files, use an absolute path. (custom-declare-variable 'org-link-file-path-type ''adaptive '(#$ . 36894) :group 'org-link :type '(choice (const relative) (const absolute) (const noabbrev) (const adaptive))) #@816 Types of links that should be activated in Org-mode files. This is a list of symbols, each leading to the activation of a certain link type. In principle, it does not hurt to turn on most link types - there may be a small gain when turning off unused link types. The types are: bracket The recommended [[link][description]] or [[link]] links with hiding. angular Links in angular brackets that may contain whitespace like <bbdb:Carsten Dominik>. plain Plain links in normal text, no whitespace, like http://google.com. radio Text that is matched by a radio target, see manual for details. tag Tag settings in a headline (link to tag search). date Time stamps (link to calendar). footnote Footnote labels. Changing this variable requires a restart of Emacs to become effective. (custom-declare-variable 'org-activate-links ''(bracket angle plain radio tag date footnote) '(#$ . 37537) :group 'org-link :type '(set :greedy t (const :tag "Double bracket links (new style)" bracket) (const :tag "Angular bracket links (old style)" angular) (const :tag "Plain text links" plain) (const :tag "Radio target matches" radio) (const :tag "Tags" tag) (const :tag "Timestamps" date) (const :tag "Footnotes" footnote))) #@264 Function to use to generate link descriptions from links. If nil the link location will be used. This function must take two parameters; the first is the link and the second the description org-insert-link has generated, and should return the description to use. (custom-declare-variable 'org-make-link-description-function 'nil '(#$ . 38789) :group 'org-link :type 'function) (custom-declare-group 'org-link-store nil "Options concerning storing links in Org-mode." :tag "Org Store Link" :group 'org-link) #@666 Format of the description part of a link to an email or usenet message. The following %-escapes will be replaced by corresponding information: %F full "From" field %f name, taken from "From" field, address if no name %T full "To" field %t first name in "To" field, address if no name %c correspondent. Usually "from NAME", but if you sent it yourself, it will be "to NAME". See also the variable `org-from-is-user-regexp'. %s subject %m message-id. You may use normal field width specification between the % and the letter. This is for example useful to limit the length of the subject. Examples: "%f on: %.30s", "Email from %f", "Email %c" (custom-declare-variable 'org-email-link-description-format '"Email %c: %.30s" '(#$ . 39303) :group 'org-link-store :type 'string) #@135 Regexp matched against the "From:" header of an email or usenet message. It should match if the message is from the user him/herself. (custom-declare-variable 'org-from-is-user-regexp '(let (r1 r2) (when (and user-mail-address (not (string= user-mail-address #1=""))) (setq r1 (concat "\\<" (regexp-quote user-mail-address) "\\>"))) (when (and user-full-name (not (string= user-full-name #1#))) (setq r2 (concat "\\<" (regexp-quote user-full-name) "\\>"))) (if (and r1 r2) (concat r1 "\\|" r2) (or r1 r2))) '(#$ . 40106) :group 'org-link-store :type 'regexp) #@1086 Non-nil means, storing a link to an Org file will use entry IDs. Note that before this variable is even considered, org-id must be loaded, to please customize `org-modules' and turn it on. The variable can have the following values: t Create an ID if needed to make a link to the current entry. create-if-interactive If `org-store-link' is called directly (interactively, as a user command), do create an ID to support the link. But when doing the job for remember, only use the ID if it already exists. The purpose of this setting is to avoid proliferation of unwanted IDs, just because you happen to be in an Org file when you call `org-remember' that automatically and preemptively creates a link. If you do want to get an ID link in a remember template to an entry not having an ID, create it first by explicitly creating a link to it, using `C-c C-l' first. use-existing Use existing ID, do not create one. nil Never use an ID to make a link, instead link using a text search for the headline text. (custom-declare-variable 'org-link-to-org-use-id ''create-if-interactive '(#$ . 40673) :group 'org-link-store :type '(choice (const :tag "Create ID to make link" t) (const :tag "Create if string link interactively" 'create-if-interactive) (const :tag "Only use existing" 'use-existing) (const :tag "Do not use ID to create link" nil))) #@351 Non-nil means, file links from `org-store-link' contain context. A search string will be added to the file name with :: as separator and used to find the context when the link is activated by the command `org-open-at-point'. Using a prefix arg to the command \[org-store-link] (`org-store-link') negates this setting for the duration of the command. (custom-declare-variable 'org-context-in-file-links 't '(#$ . 42101) :group 'org-link-store :type 'boolean) #@491 Non-nil means, keep link in list for entire session. The command `org-store-link' adds a link pointing to the current location to an internal list. These links accumulate during a session. The command `org-insert-link' can be used to insert links into any Org-mode file (offering completion for all stored links). When this option is nil, every link which has been inserted once using \[org-insert-link] will be removed from the list, to make completing the unused links more efficient. (custom-declare-variable 'org-keep-stored-link-after-insertion 'nil '(#$ . 42566) :group 'org-link-store :type 'boolean) (custom-declare-group 'org-link-follow nil "Options concerning following links in Org-mode." :tag "Org Follow Link" :group 'org-link) #@589 Function to translate links with different syntax to Org syntax. This can be used to translate links created for example by the Planner or emacs-wiki packages to Org syntax. The function must accept two parameters, a TYPE containing the link protocol name like "rmail" or "gnus" as a string, and the linked path, which is everything after the link protocol. It should return a cons with possibly modified values of type and path. Org contains a function for this, so if you set this variable to `org-translate-link-from-planner', you should be able follow many links created by planner. (custom-declare-variable 'org-link-translation-function 'nil '(#$ . 43318) :group 'org-link-follow :type 'function) #@50 Hook that is run after a link has been followed. (custom-declare-variable 'org-follow-link-hook 'nil '(#$ . 44028) :group 'org-link-follow :type 'hook) #@92 Non-nil means, on links TAB will follow the link. Needs to be set before org.el is loaded. (custom-declare-variable 'org-tab-follows-link 'nil '(#$ . 44186) :group 'org-link-follow :type 'boolean) #@92 Non-nil means, on links RET will follow the link. Needs to be set before org.el is loaded. (custom-declare-variable 'org-return-follows-link 'nil '(#$ . 44389) :group 'org-link-follow :type 'boolean) #@166 Non-nil means, mouse-1 on a link will follow the link. 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-mouse-1-follows-link '(if (boundp 'mouse-1-click-follows-link) mouse-1-click-follows-link t) '(#$ . 44596) :group 'org-link-follow :type 'boolean) #@119 Number of different positions to be recorded in the ring Changing this requires a restart of Emacs to work correctly. (custom-declare-variable 'org-mark-ring-length '4 '(#$ . 44945) :group 'org-link-follow :type 'integer) #@620 Setup the frame configuration for following links. When following a link with Emacs, it may often be useful to display this link in another window or frame. This variable can be used to set this up for the different types of links. For VM, use any of `vm-visit-folder' `vm-visit-folder-other-frame' For Gnus, use any of `gnus' `gnus-other-frame' `org-gnus-no-new-news' For FILE, use any of `find-file' `find-file-other-window' `find-file-other-frame' For the calendar, use the variable `calendar-setup'. For BBDB, it is currently only possible to display the matches in another window. (custom-declare-variable 'org-link-frame-setup ''((vm . vm-visit-folder-other-frame) (gnus . gnus-other-frame) (file . find-file-other-window)) '(#$ . 45174) :group 'org-link-follow :type '(list (cons (const vm) (choice (const vm-visit-folder) (const vm-visit-folder-other-window) (const vm-visit-folder-other-frame))) (cons (const gnus) (choice (const gnus) (const gnus-other-frame) (const org-gnus-no-new-news))) (cons (const file) (choice (const find-file) (const find-file-other-window) (const find-file-other-frame))))) #@461 Non-nil means, use indirect buffer to display infile links. Activating internal links (from one location in a file to another location in the same file) normally just jumps to the location. When the link is activated with a C-u prefix (or with mouse-3), the link is displayed in another window. When this option is set, the other window actually displays an indirect buffer clone of the current buffer, to avoid any visibility changes to the current buffer. (custom-declare-variable 'org-display-internal-link-with-indirect-buffer 'nil '(#$ . 46325) :group 'org-link-follow :type 'boolean) #@100 Non-nil means, `org-open-file' will open non-existing files. When nil, an error will be generated. (custom-declare-variable 'org-open-non-existing-files 'nil '(#$ . 46924) :group 'org-link-follow :type 'boolean) #@169 Non-nil means, a link to a directory really means to index.org. When nil, following a directory link will run dired or open a finder/explorer window on that directory. (custom-declare-variable 'org-open-directory-means-index-dot-org 'nil '(#$ . 47143) :group 'org-link-follow :type 'boolean) #@345 Function and arguments to call for following mailto links. This is a list with the first element being a lisp function, and the remaining elements being arguments to the function. In string arguments, %a will be replaced by the address, and %s will be replaced by the subject if one was given like in <mailto:arthur@galaxy.org::this subject>. (custom-declare-variable 'org-link-mailto-program ''(browse-url "mailto:%a?subject=%s") '(#$ . 47442) :group 'org-link-follow :type '(choice (const :tag "browse-url" (browse-url-mail "mailto:%a?subject=%s")) (const :tag "compose-mail" (compose-mail "%a" "%s")) (const :tag "message-mail" (message-mail "%a" "%s")) (cons :tag "other" (function) (repeat :tag "argument" sexp)))) #@457 Non-nil means, ask for confirmation before executing shell links. Shell links can be dangerous: just think about a link [[shell:rm -rf ~/*][Google Search]] This link would show up in your Org-mode document as "Google Search", but really it would remove your entire home directory. Therefore we advise against setting this variable to nil. Just change it to `y-or-n-p' of you want to confirm with a single keystroke rather than having to type "yes". (custom-declare-variable 'org-confirm-shell-link-function ''yes-or-no-p '(#$ . 48170) :group 'org-link-follow :type '(choice (const :tag "with yes-or-no (safer)" yes-or-no-p) (const :tag "with y-or-n (faster)" y-or-n-p) (const :tag "no confirmation (dangerous)" nil))) #@480 Non-nil means, ask for confirmation before executing Emacs Lisp links. Elisp links can be dangerous: just think about a link [[elisp:(shell-command "rm -rf ~/*")][Google Search]] This link would show up in your Org-mode document as "Google Search", but really it would remove your entire home directory. Therefore we advise against setting this variable to nil. Just change it to `y-or-n-p' of you want to confirm with a single keystroke rather than having to type "yes". (custom-declare-variable 'org-confirm-elisp-link-function ''yes-or-no-p '(#$ . 48902) :group 'org-link-follow :type '(choice (const :tag "with yes-or-no (safer)" yes-or-no-p) (const :tag "with y-or-n (faster)" y-or-n-p) (const :tag "no confirmation (dangerous)" nil))) #@79 Default file applications on a UNIX or GNU/Linux system. See `org-file-apps'. (defconst org-file-apps-defaults-gnu '((remote . emacs) (system . mailcap) (t . mailcap)) (#$ . 49656)) #@200 Default file applications on a MacOS X system. The system "open" is known as a default, but we use X11 applications for some files for which the OS does not have a good default. See `org-file-apps'. (defconst org-file-apps-defaults-macosx '((remote . emacs) (t . "open %s") (system . "open %s") ("ps.gz" . "gv %s") ("eps.gz" . "gv %s") ("dvi" . "xdvi %s") ("fig" . "xfig %s")) (#$ . 49845)) #@114 Default file applications on a Windows NT system. The system "open" is used for most files. See `org-file-apps'. (defconst org-file-apps-defaults-windowsnt (byte-code "\300\301\302\303\304EB\305\302\303\304EBE\207" [(remote . emacs) t w32-shell-execute "open" file system] 6) (#$ . 50243)) #@2614 External applications for opening `file:path' items in a document. Org-mode uses system defaults for different file types, but you can use this variable to set the application for a given file extension. The entries in this list are cons cells where the car identifies files and the cdr the corresponding command. Possible values for the file identifier are "regex" Regular expression matched against the file name. For backward compatibility, this can also be a string with only alphanumeric characters, which is then interpreted as an extension. `directory' Matches a directory `remote' Matches a remote file, accessible through tramp or efs. Remote files most likely should be visited through Emacs because external applications cannot handle such paths. `auto-mode' Matches files that are matched by any entry in `auto-mode-alist', so all files Emacs knows how to handle. Using this with command `emacs' will open most files in Emacs. Beware that this will also open html files inside Emacs, unless you add ("html" . default) to the list as well. t Default for files not matched by any of the other options. `system' The system command to open files, like `open' on Windows and Mac OS X, and mailcap under GNU/Linux. This is the command that will be selected if you call `C-c C-o' with a double `C-u C-u' prefix. Possible values for the command are: `emacs' The file will be visited by the current Emacs process. `default' Use the default application for this file type, which is the association for t in the list, most likely in the system-specific part. This can be used to overrule an unwanted setting in the system-specific variable. `system' Use the system command for opening files, like "open". This command is specified by the entry whose car is `system'. Most likely, the system-specific version of this variable does define this command, but you can overrule/replace it here. string A command to be executed by a shell; %s will be replaced by the path to the file. sexp A Lisp form which will be evaluated. The file path will be available in the Lisp variable `file'. For more examples, see the system specific constants `org-file-apps-defaults-macosx' `org-file-apps-defaults-windowsnt' `org-file-apps-defaults-gnu'. (custom-declare-variable 'org-file-apps ''((auto-mode . emacs) ("\\.x?html?\\'" . default) ("\\.pdf\\'" . default)) '(#$ . 50541) :group 'org-link-follow :type '(repeat (cons (choice :value #1="" (string :tag "Extension") (const :tag "System command to open files" system) (const :tag "Default for unrecognized files" t) (const :tag "Remote file" remote) (const :tag "Links to a directory" directory) (const :tag "Any files that have Emacs modes" auto-mode)) (choice :value #1# (const :tag "Visit with Emacs" emacs) (const :tag "Use default" default) (const :tag "Use the system command" system) (string :tag "Command") (sexp :tag "Lisp form"))))) (custom-declare-group 'org-refile nil "Options concerning refiling entries in Org-mode." :tag "Org Refile" :group 'org) #@126 Directory with org files. This directory will be used as default to prompt for org files. Used by the hooks for remember.el. (custom-declare-variable 'org-directory '"~/org" '(#$ . 53929) :group 'org-refile :group 'org-remember :type 'directory) #@228 Default target for storing notes. Used by the hooks for remember.el. This can be a string, or nil to mean the value of `remember-data-file'. You can set this on a per-template basis with the variable `org-remember-templates'. (custom-declare-variable 'org-default-notes-file '(convert-standard-filename "~/.notes") '(#$ . 54182) :group 'org-refile :group 'org-remember :type '(choice (const :tag "Default from remember-data-file" nil) file)) #@492 The default interface to be used for `org-goto'. Allowed values are: outline The interface shows an outline of the relevant file and the correct heading is found by moving through the outline or by searching with incremental search. outline-path-completion Headlines in the current buffer are offered via completion. This is the interface also used by the refile command. (custom-declare-variable 'org-goto-interface ''outline '(#$ . 54632) :group 'org-refile :type '(choice (const :tag "Outline" outline) (const :tag "Outline-path-completion" outline-path-completion))) #@77 Maximum level to be considered when running org-goto with refile interface. (custom-declare-variable 'org-goto-max-level '5 '(#$ . 55328) :group 'org-refile :type 'number) #@246 Non-nil means, store new notes at the beginning of a file or entry. When nil, new notes will be filed to the end of a file or entry. This can also be a list with cons cells of regular expressions that are matched against file names, and values. (custom-declare-variable 'org-reverse-note-order 'nil '(#$ . 55507) :group 'org-remember :group 'org-refile :type '(choice (const :tag "Reverse always" t) (const :tag "Reverse never" nil) (repeat :tag "By file name regexp" (cons regexp boolean)))) #@1163 Targets for refiling entries with \[org-refile]. This is list of cons cells. Each cell contains: - a specification of the files to be considered, either a list of files, or a symbol whose function or variable value will be used to retrieve a file name or a list of file names. If you use `org-agenda-files' for that, all agenda files will be scanned for targets. Nil means, consider headings in the current buffer. - A specification of how to select find candidate refile targets. This may be any of - a cons cell (:tag . "TAG") to identify refile targets by a tag. This tag has to be present in all target headlines, inheritance will not be considered. - a cons cell (:todo . "KEYWORD") to identify refile targets by todo keyword. - a cons cell (:regexp . "REGEXP") with a regular expression matching headlines that are refiling targets. - a cons cell (:level . N). Any headline of level N is considered a target. - a cons cell (:maxlevel . N). Any headline with level <= N is a target. When this variable is nil, all top-level headlines in the current buffer are used, equivalent to the value `((nil . (:level . 1))'. (custom-declare-variable 'org-refile-targets 'nil '(#$ . 56008) :group 'org-refile :type '(repeat (cons (choice :value org-agenda-files (const :tag "All agenda files" org-agenda-files) (const :tag "Current buffer" nil) (function) (variable) (file)) (choice :tag "Identify target headline by" (cons :tag "Specific tag" (const :value :tag) (string)) (cons :tag "TODO keyword" (const :value :todo) (string)) (cons :tag "Regular expression" (const :value :regexp) (regexp)) (cons :tag "Level number" (const :value :level) (integer)) (cons :tag "Max Level number" (const :value :maxlevel) (integer)))))) #@254 Non-nil means, provide refile targets as paths. So a level 3 headline will be available as level1/level2/level3. When the value is `file', also include the file name (without directory) into the path. When `full-file-path', include the full file path. (custom-declare-variable 'org-refile-use-outline-path 'nil '(#$ . 57776) :group 'org-refile :type '(choice (const :tag "Not" nil) (const :tag "Yes" t) (const :tag "Start with file name" file) (const :tag "Start with full file path" full-file-path))) #@518 Non-nil means, complete the outline path in hierarchical steps. When Org-mode uses the refile interface to select an outline path (see variable `org-refile-use-outline-path'), the completion of the path can be done is a single go, or if can be done in steps down the headline hierarchy. Going in steps is probably the best if you do not use a special completion package like `ido' or `icicles'. However, when using these packages, going in one step can be very fast, while still showing the whole path to the entry. (custom-declare-variable 'org-outline-path-complete-in-steps 't '(#$ . 58286) :group 'org-refile :type 'boolean) (byte-code "\300\301\302\303\304\305\306\307&\210\300\310\302\311\304\312\306\313&\207" [custom-declare-group org-todo nil "Options concerning TODO items in Org-mode." :tag "Org TODO" :group org org-progress "Options concerning Progress logging in Org-mode." "Org Progress" org-time] 8) #@2129 List of TODO entry keyword sequences and their interpretation. \<org-mode-map>This is a list of sequences. Each sequence starts with a symbol, either `sequence' or `type', indicating if the keywords should be interpreted as a sequence of action steps, or as different types of TODO items. The first keywords are states requiring action - these states will select a headline for inclusion into the global TODO list Org-mode produces. If one of the "keywords" is the vertical bat "|" the remaining keywords signify that no further action is necessary. If "|" is not found, the last keyword is treated as the only DONE state of the sequence. The command \[org-todo] cycles an entry through these states, and one additional state where no keyword is present. For details about this cycling, see the manual. TODO keywords and interpretation can also be set on a per-file basis with the special #+SEQ_TODO and #+TYP_TODO lines. Each keyword can optionally specify a character for fast state selection (in combination with the variable `org-use-fast-todo-selection') and specifiers for state change logging, using the same syntax that is used in the "#+TODO:" lines. For example, "WAIT(w)" says that the WAIT state can be selected with the "w" key. "WAIT(w!)" indicates to record a time stamp each time this state is selected. Each keyword may also specify if a timestamp or a note should be recorded when entering or leaving the state, by adding additional characters in the parenthesis after the keyword. This looks like this: "WAIT(w@/!)". "@" means to add a note (with time), "!" means to record only the time of the state change. With X and Y being either "@" or "!", "X/Y" means use X when entering the state, and use Y when leaving the state if and only if the *target* state does not define X. You may omit any of the fast-selection key or X or /Y, so WAIT(w@), WAIT(w/@) and WAIT(@/@) are all valid. For backward compatibility, this variable may also be just a list of keywords - in this case the interpretation (sequence or type) will be taken from the (otherwise obsolete) variable `org-todo-interpretation'. (custom-declare-variable 'org-todo-keywords ''((sequence "TODO" "DONE")) '(#$ . 59213) :group 'org-todo :group 'org-keywords :type '(choice (repeat :tag "Old syntax, just keywords" (string :tag "Keyword")) (repeat :tag "New syntax" (cons (choice :tag "Interpretation" (const :tag "Sequence (cycling hits every state)" sequence) (const :tag "Type (cycling directly to DONE)" type)) (repeat (string :tag "Keyword")))))) #@48 All TODO and DONE keywords active in a buffer. (defvar org-todo-keywords-1 nil (#$ . 61769)) (byte-code "\301\302!\210\303B\304\303!\204 \305\303\306\"\210\307B\304\307!\204\"