?
Current Path : /usr/share/emacs/24.3/lisp/ |
Linux gator3171.hostgator.com 4.19.286-203.ELK.el7.x86_64 #1 SMP Wed Jun 14 04:33:55 CDT 2023 x86_64 |
Current File : //usr/share/emacs/24.3/lisp/allout.elc |
;ELC ;;; Compiled by mockbuild@buildfarm06-new.corp.cloudlinux.com on Fri Oct 11 10:06:10 2024 ;;; from file /builddir/build/BUILD/emacs-24.3/lisp/allout.el ;;; in Emacs version 24.3.1 ;;; with all optimizations. ;;; This file uses dynamic docstrings, first added in Emacs 19.29. ;;; This file does not contain utf-8 non-ASCII characters, ;;; and so can be loaded in Emacs versions earlier than 23. ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; (byte-code "\300\301!\210\302\303\304\305\306\307\310\311&\210\302\312\304\313\310\303%\207" [require overlay custom-declare-group allout nil "Extensive outline minor-mode, for use stand-alone and with other modes.\n\nSee Allout Auto Activation for automatic activation." :prefix "allout-" :group outlines allout-keybindings "Allout outline mode keyboard bindings configuration."] 8) #@212 Keybindings place-holder for (allout) outline minor mode. Do NOT set the value of this variable. Instead, customize `allout-command-prefix', `allout-prefixed-keybindings', and `allout-unprefixed-keybindings'. (defvar allout-mode-map 'allout-mode-map (#$ . 935)) #@192 Keymap for allout outline minor mode. Do NOT set the value of this variable. Instead, customize `allout-command-prefix', `allout-prefixed-keybindings', and `allout-unprefixed-keybindings'. (defvar allout-mode-map-value nil (#$ . 1206)) (defalias 'allout-mode-map allout-mode-map-value) #@264 Create the allout keymap according to the keybinding specs, and set it. Useful standalone or to effect customizations of the respective allout-mode keybinding variables, `allout-command-prefix', `allout-prefixed-keybindings', and `allout-unprefixed-keybindings' (defalias 'allout-compose-and-institute-keymap #[(&optional varname value) "\203 \306 \"\210\307 \310\303!\2039 \311\211\2038 @\312\n\313\314\f@!@\"\f\211A@)#\210 A\211\204 *\310\315!\203c \311\211\203b @\312\n\314\f@!@\f\211A@)#\210 A\211\204H *\316\317\320\n$\210\316\321\320\n$\210\316\322\323\n$\210\316\324\323\n$\210\325\n!)\207" [varname value map allout-prefixed-keybindings entry --dolist-tail-- set-default make-sparse-keymap boundp nil define-key vconcat read-from-string allout-unprefixed-keybindings substitute-key-definition beginning-of-line allout-beginning-of-line move-beginning-of-line end-of-line allout-end-of-line move-end-of-line allout-institute-keymap allout-command-prefix x global-map] 7 (#$ . 1501)]) #@61 Associate allout-mode bindings with allout as a minor mode. (defalias 'allout-institute-keymap #[(map) "\n M\207" [map allout-mode-map-value allout-mode-map] 2 (#$ . 2531)]) (byte-code "\300 \210\301\302\303\304\305\306\307\310\311\300& \210\312\313\314\315\305\316%\210\301\317\320\321\322\323\305\313\307\310\311\300&\210\301\324\325\326\322\323\305\313\307\310\311\300&\207" [allout-compose-and-institute-keymap custom-declare-variable allout-command-prefix " " "Key sequence to be used as prefix for outline mode command key bindings.\n\nDefault is '<space>'; just '' is more short-and-sweet, if you're\nwilling to let allout use a bunch of keybindings." :type string :group allout-keybindings :set define-widget allout-keybindings-binding lazy "Structure of allout keybindings customization items." (repeat (list (string :tag "Key" :value "[(meta control shift ?f)]") (function :tag "Function name" :value allout-forward-current-level))) allout-prefixed-keybindings '(("[(control ?n)]" allout-next-visible-heading) ("[(control ?p)]" allout-previous-visible-heading) ("[(control ?u)]" allout-up-current-level) ("[(control ?f)]" allout-forward-current-level) ("[(control ?b)]" allout-backward-current-level) ("[(control ?a)]" allout-beginning-of-current-entry) ("[(control ?e)]" allout-end-of-entry) ("[(control ?i)]" allout-show-children) ("[(control ?s)]" allout-show-current-subtree) ("[(control ?t)]" allout-toggle-current-subtree-exposure) ("[?h]" allout-hide-current-subtree) ("[(control ?o)]" allout-show-current-entry) ("[?!]" allout-show-all) ("[?x]" allout-toggle-current-subtree-encryption) ("[? ]" allout-open-sibtopic) ("[?.]" allout-open-subtopic) ("[?,]" allout-open-supertopic) ("[?']" allout-shift-in) ("[?>]" allout-shift-in) ("[?<]" allout-shift-out) ("[(control ?m)]" allout-rebullet-topic) ("[?*]" allout-rebullet-current-heading) ("[?#]" allout-number-siblings) ("[(control ?k)]" allout-kill-topic) ("[(meta ?k)]" allout-copy-topic-as-kill) ("[?@]" allout-resolve-xref) ("[?=?c]" allout-copy-exposed-to-buffer) ("[?=?i]" allout-indented-exposed-to-buffer) ("[?=?t]" allout-latexify-exposed) ("[?=?p]" allout-flatten-exposed-to-buffer)) "Allout-mode key bindings that are prefixed with `allout-command-prefix'.\n\nSee `allout-unprefixed-keybindings' for the list of keybindings\nthat are not prefixed.\n\nUse vector format for the keys:\n - put literal keys after a '?' question mark, eg: '?a', '?.'\n - enclose control, shift, or meta-modified keys as sequences within\n parentheses, with the literal key, as above, preceded by the name(s)\n of the modifiers, eg: [(control ?a)]\nSee the existing keys for examples.\n\nFunctions can be bound to multiple keys, but binding keys to\nmultiple functions will not work - the last binding for a key\nprevails." :version "24.1" allout-unprefixed-keybindings '(("[(control ?k)]" allout-kill-line) ("[(meta ?k)]" allout-copy-line-as-kill) ("[(control ?y)]" allout-yank) ("[(meta ?y)]" allout-yank-pop)) "Allout-mode functions bound to keys without any added prefix.\n\nThis is in contrast to the majority of allout-mode bindings on\n`allout-prefixed-bindings', whose bindings are created with a\npreceding command key.\n\nUse vector format for the keys:\n - put literal keys after a '?' question mark, eg: '?a', '?.'\n - enclose control, shift, or meta-modified keys as sequences within\n parentheses, with the literal key, as above, preceded by the name(s)\n of the modifiers, eg: [(control ?a)]\nSee the existing keys for examples."] 12) #@105 Institute `allout-auto-activation'. Intended to be used as the `allout-auto-activation' :set function. (defalias 'allout-auto-activation-helper #[(var value) "\302 \"\210\303 \207" [var value set-default allout-setup] 3 (#$ . 6069)]) #@273 Do fundamental Emacs session for allout auto-activation. Establishes allout processing as part of visiting a file if `allout-auto-activation' is non-nil, or removes it otherwise. The proper way to use this is through customizing the setting of `allout-auto-activation'. (defalias 'allout-setup #[nil "\204 \301\302\303\"\207\304\302\303\"\207" [allout-auto-activation remove-hook find-file-hook allout-find-file-hook add-hook] 3 (#$ . 6312)]) (byte-code "\300\301\302\303\304\305\306\307\310\311& \210\312 \210\300\313\314\315\306\316\310\311&\210\317\316\320\321\306\322%\210\300\323\302\324\306\325\310\311&\210\326\323!\210\300\327\302\330\331\332\306\325\310\311& \210\326\327!\210\300\333\334\335\306\325\310\311&\210\326\333!\210\336\333\337\340\341!\203_ \341\202` \342#\210\300\343\344\345\306\346\310\311&\210\326\343!\210\336\343\337\347#\210\300\350\302\351\306\325\310\311&\210\326\350!\210\336\350\337\340\341!\203\223 \341\202\224 \352#\210\300\353\334\354\306\325\310\311&\210\300\355\334\356\306\325\310\311&\210\300\357\360\361\306\362\310\311&\210\326\357!\210\336\357\337\363#\210\300\364\365\366\306\362\310\311&\210\326\364!\210\336\364\337\363#\210\300\367\370\371\306\362\310\311&\210\326\367!\210\336\367\337\363#\210\300\372\373\374\306\362\310\311&\210\326\372!\210\336\372\337\363#\210\300\375\334\376\306\377\310\311&\210\336\375\337\201@ #\207" [custom-declare-variable allout-auto-activation nil "Configure allout outline mode auto-activation.\n\nControl whether and how allout outline mode is automatically\nactivated when files are visited with non-nil buffer-specific\nfile variable `allout-layout'.\n\nWhen allout-auto-activation is \"On\" (t), allout mode is\nactivated in buffers with non-nil `allout-layout', and the\nspecified layout is applied.\n\nWith value \"ask\", auto-mode-activation is enabled, and endorsement for\nperforming auto-layout is asked of the user each time.\n\nWith value \"activate\", only auto-mode-activation is enabled.\nAuto-layout is not.\n\nWith value nil, inhibit any automatic allout-mode activation." :set allout-auto-activation-helper :type (choice (const :tag "On" t) (const :tag "Ask about layout" "ask") (const :tag "Mode only" "activate") (const :tag "Off" nil)) :group allout allout-setup allout-default-layout '(-2 : 0) "Default allout outline layout specification.\n\nThis setting specifies the outline exposure to use when\n`allout-layout' has the local value `t'. This docstring describes the\nlayout specifications.\n\nA list value specifies a default layout for the current buffer,\nto be applied upon activation of `allout-mode'. Any non-nil\nvalue will automatically trigger `allout-mode', provided\n`allout-auto-activation' has been customized to enable it.\n\nThe types of elements in the layout specification are:\n\n INTEGER -- dictate the relative depth to open the corresponding topic(s),\n where:\n -- negative numbers force the topic to be closed before opening\n to the absolute value of the number, so all siblings are open\n only to that level.\n -- positive numbers open to the relative depth indicated by the\n number, but do not force already opened subtopics to be closed.\n -- 0 means to close topic -- hide all subitems.\n : -- repeat spec -- apply the preceding element to all siblings at\n current level, *up to* those siblings that would be covered by specs\n following the `:' on the list. Ie, apply to all topics at level but\n trailing ones accounted for by trailing specs. (Only the first of\n multiple colons at the same level is honored -- later ones are ignored.)\n * -- completely exposes the topic, including bodies\n + -- exposes all subtopics, but not the bodies\n - -- exposes the body of the corresponding topic, but not subtopics\n LIST -- a nested layout spec, to be applied intricately to its\n corresponding item(s)\n\nExamples:\n (-2 : 0)\n Collapse the top-level topics to show their children and\n grandchildren, but completely collapse the final top-level topic.\n (-1 () : 1 0)\n Close the first topic so only the immediate subtopics are shown,\n leave the subsequent topics exposed as they are until the second\n second to last topic, which is exposed at least one level, and\n completely close the last topic.\n (-2 : -1 *)\n Expose children and grandchildren of all topics at current\n level except the last two; expose children of the second to\n last and completely expose the last one, including its subtopics.\n\nSee `allout-expose-topic' for more about the exposure process.\n\nAlso, allout's mode-specific provisions will make topic prefixes default\nto the comment-start string, if any, of the language of the file. This\nis modulo the setting of `allout-use-mode-specific-leader', which see." allout-layout-type define-widget lazy "Allout layout format customization basic building blocks." (repeat (choice (integer :tag "integer (<= zero is strict)") (const :tag ": (repeat prior)" :) (const :tag "* (completely expose)" *) (const :tag "+ (expose all offspring, headlines only)" +) (const :tag "- (expose topic body but not offspring)" -) (allout-layout-type :tag "<Nested layout>"))) allout-inhibit-auto-fill "If non-nil, auto-fill will be inhibited in the allout buffers.\n\nYou can customize this setting to set it for all allout buffers, or set it\nin individual buffers if you want to inhibit auto-fill only in particular\nbuffers. (You could use a function on `allout-mode-hook' to inhibit\nauto-fill according, eg, to the major mode.)\n\nIf you don't set this and auto-fill-mode is enabled, allout will use the\nvalue that `normal-auto-fill-function', if any, when allout mode starts, or\nelse allout's special hanging-indent maintaining auto-fill function,\n`allout-auto-fill'." boolean make-variable-buffer-local allout-inhibit-auto-fill-on-headline "If non-nil, auto-fill will be inhibited while on topic's header line." :version "24.1" allout-use-hanging-indents t "If non-nil, topic body text auto-indent defaults to indent of the header.\nIe, it is indented to be just past the header prefix. This is\nrelevant mostly for use with `indented-text-mode', or other situations\nwhere auto-fill occurs." put safe-local-variable fboundp booleanp #[(x) "\301\235\207" [x (t nil)] 2] allout-reindent-bodies (if allout-use-hanging-indents 'text) "Non-nil enables auto-adjust of topic body hanging indent with depth shifts.\n\nWhen active, topic body lines that are indented even with or beyond\ntheir topic header are reindented to correspond with depth shifts of\nthe header.\n\nA value of t enables reindent in non-programming-code buffers, ie\nthose that do not have the variable `comment-start' set. A value of\n`force' enables reindent whether or not `comment-start' is set." (choice (const nil) (const t) (const text) (const force)) #[(x) "\301>\207" [x (nil t text force)] 2] allout-show-bodies "If non-nil, show entire body when exposing a topic, rather than\njust the header." #[(x) "\301\235\207" [x (t nil)] 2] allout-beginning-of-line-cycles "If non-nil, \\[allout-beginning-of-line] will cycle through smart-placement options.\n\nCycling only happens on when the command is repeated, not when it\nfollows a different command.\n\nSmart-placement means that repeated calls to this function will\nadvance as follows:\n\n - if the cursor is on a non-headline body line and not on the first column:\n then it goes to the first column\n - if the cursor is on the first column of a non-headline body line:\n then it goes to the start of the headline within the item body\n - if the cursor is on the headline and not the start of the headline:\n then it goes to the start of the headline\n - if the cursor is on the start of the headline:\n then it goes to the bullet character (for hotspot navigation)\n - if the cursor is on the bullet character:\n then it goes to the first column of that line (the headline)\n - if the cursor is on the first column of the headline:\n then it goes to the start of the headline within the item body.\n\nIn this fashion, you can use the beginning-of-line command to do\nits normal job and then, when repeated, advance through the\nentry, cycling back to start.\n\nIf this configuration variable is nil, then the cursor is just\nadvanced to the beginning of the line and remains there on\nrepeated calls." allout-end-of-line-cycles "If non-nil, \\[allout-end-of-line] will cycle through smart-placement options.\n\nCycling only happens on when the command is repeated, not when it\nfollows a different command.\n\nSmart placement means that repeated calls to this function will\nadvance as follows:\n\n - if the cursor is not on the end-of-line,\n then it goes to the end-of-line\n - if the cursor is on the end-of-line but not the end-of-entry,\n then it goes to the end-of-entry, exposing it if necessary\n - if the cursor is on the end-of-entry,\n then it goes to the end of the head line\n\nIn this fashion, you can use the end-of-line command to do its\nnormal job and then, when repeated, advance through the entry,\ncycling back to start.\n\nIf this configuration variable is nil, then the cursor is just\nadvanced to the end of the line and remains there on repeated\ncalls." allout-header-prefix "." "Leading string which helps distinguish topic headers.\n\nOutline topic header lines are identified by a leading topic\nheader prefix, which mostly have the value of this var at their front.\nLevel 1 topics are exceptions. They consist of only a single\ncharacter, which is typically set to the `allout-primary-bullet'." string stringp allout-primary-bullet "*" "Bullet used for top-level outline topics.\n\nOutline topic header lines are identified by a leading topic header\nprefix, which is concluded by bullets that includes the value of this\nvar and the respective allout-*-bullets-string vars.\n\nThe value of an asterisk (`*') provides for backwards compatibility\nwith the original Emacs outline mode. See `allout-plain-bullets-string'\nand `allout-distinctive-bullets-string' for the range of available\nbullets." allout-plain-bullets-string ".," "The bullets normally used in outline topic prefixes.\n\nSee `allout-distinctive-bullets-string' for the other kind of\nbullets.\n\nDO NOT include the close-square-bracket, `]', as a bullet.\n\nOutline mode has to be reactivated in order for changes to the value\nof this var to take effect." allout-distinctive-bullets-string "*+-=>()[{}&!?#%\"X@$~_\\:;^" "Persistent outline header bullets used to distinguish special topics.\n\nThese bullets are distinguish topics with particular character.\nThey are not used by default in the topic creation routines, but\nare offered as options when you modify topic creation with a\nuniversal argument (\\[universal-argument]), or during rebulleting (\\[allout-rebullet-current-heading]).\n\nDistinctive bullets are not cycled when topics are shifted or\notherwise automatically rebulleted, so their marking is\npersistent until deliberately changed. Their significance is\npurely by convention, however. Some conventions suggest\nthemselves:\n\n `(' - open paren -- an aside or incidental point\n `?' - question mark -- uncertain or outright question\n `!' - exclamation point/bang -- emphatic\n `[' - open square bracket -- meta-note, about item instead of item's subject\n `\"' - double quote -- a quotation or other citation\n `=' - equal sign -- an assignment, some kind of definition\n `^' - carat -- relates to something above\n\nSome are more elusive, but their rationale may be recognizable:\n\n `+' - plus -- pending consideration, completion\n `_' - underscore -- done, completed\n `&' - ampersand -- addendum, furthermore\n\n(Some other non-plain bullets have special meaning to the\nsoftware. By default:\n\n `~' marks encryptable topics -- see `allout-topic-encryption-bullet'\n `#' marks auto-numbered bullets -- see `allout-numbered-bullet'.)\n\nSee `allout-plain-bullets-string' for the standard, alternating\nbullets.\n\nYou must run `set-allout-regexp' in order for outline mode to\nadopt changes of this value.\n\nDO NOT include the close-square-bracket, `]', on either of the bullet\nstrings." allout-use-mode-specific-leader "When non-nil, use mode-specific topic-header prefixes.\n\nAllout outline mode will use the mode-specific `allout-mode-leaders' or\ncomment-start string, if any, to lead the topic prefix string, so topic\nheaders look like comments in the programming language. It will also use\nthe comment-start string, with an '_' appended, for `allout-primary-bullet'.\n\nString values are used as literals, not regular expressions, so\ndo not escape any regular-expression characters.\n\nValue t means to first check for assoc value in `allout-mode-leaders'\nalist, then use comment-start string, if any, then use default (`.').\n(See note about use of comment-start strings, below.)\n\nSet to the symbol for either of `allout-mode-leaders' or\n`comment-start' to use only one of them, respectively.\n\nValue nil means to always use the default (`.') and leave\n`allout-primary-bullet' unaltered.\n\ncomment-start strings that do not end in spaces are tripled in\nthe header-prefix, and an `_' underscore is tacked on the end, to\ndistinguish them from regular comment strings. comment-start\nstrings that do end in spaces are not tripled, but an underscore\nis substituted for the space. [This presumes that the space is\nfor appearance, not comment syntax. You can use\n`allout-mode-leaders' to override this behavior, when\nundesired.]" (choice (const t) (const nil) string (const allout-mode-leaders) (const comment-start)) #[(x) "\301>\206 ;\207" [x (t nil allout-mode-leaders comment-start)] 2]] 10) #@482 Specific allout-prefix leading strings per major modes. Use this if the mode's comment-start string isn't what you prefer, or if the mode lacks a comment-start string. See `allout-use-mode-specific-leader' for more details. If you're constructing a string that will comment-out outline structuring so it can be included in program code, append an extra character, like an "_" underscore, to distinguish the lead string from regular comments that start at the beginning-of-line. (defvar allout-mode-leaders nil (#$ . 20142)) (byte-code "\302\303\304\305\306\307\310\311&\210\312\303!\210\313\303\314\315\316!\203 \316\202 \317#\210\302\320\321\322\306\307\310\311&\210\312\320!\210\313\320\314\315\316!\203; \316\202<