| Server IP : 217.160.0.212 / Your IP : 216.73.216.71 Web Server : Apache System : Linux www 6.18.52-i1-ampere #1203 SMP Mon Sep 14 18:29:59 CEST 2026 aarch64 User : sws1073854427 ( 1073854427) PHP Version : 8.4.23 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : OFF | Pkexec : OFF Directory : /usr/share/emacs/28.2/lisp/ |
Upload File : |
;ELC
;;; Compiled
;;; in Emacs version 28.2
;;; with all optimizations.
(byte-code "\300\301\302\303\304\305\306\307&\210\300\310\302\311\306\301%\207" [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 (#$ . 441))
#@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 (#$ . 712))
(defalias 'allout-mode-map allout-mode-map-value)
#@296 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'
(fn &optional VARNAME VALUE)
(defalias 'allout-compose-and-institute-keymap #[512 "\203 \304\"\210\305 \306\300!\203/ \211\203. \211@\307\310 \311@!@\"A@#\210A\266\202\202 \210\306\302!\203P \n\211\203O \211@\307\311@!@A@#\210A\266\202\2026 \210\312\313\314$\210\312\315\314$\210\312\316\317$\210\312\320\317$\210\321!\207" [allout-prefixed-keybindings allout-command-prefix allout-unprefixed-keybindings global-map set-default make-sparse-keymap boundp define-key vconcat read-from-string 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] 11 (#$ . 1006)])
#@73 Associate `allout-mode' bindings with allout as a minor mode.
(fn MAP)
(defalias 'allout-institute-keymap #[257 "\211 M\207" [allout-mode-map-value allout-mode-map] 3 (#$ . 1973)])
(byte-code "\300 \210\301\302\303\304\305DD\306\307\310\311\312\313\300& \210\314\315\316\317\307\320%\210\301\321\303\304\322DD\323\324\325\307\315\311\312\313\300&\210\301\326\303\304\327DD\330\324\325\307\315\311\312\313\300&\207" [allout-compose-and-institute-keymap custom-declare-variable allout-command-prefix funcall function #[0 "\300\207" [" "] 1 #1=""] "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 #[0 "\300\207" [(("[(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))] 1 #1#] "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 #[0 "\300\207" [(("[(control ?k)]" allout-kill-line) ("[(meta ?k)]" allout-copy-line-as-kill) ("[(control ?y)]" allout-yank) ("[(meta ?y)]" allout-yank-pop))] 1 #1#] "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-keybindings', 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)
#@121 Institute `allout-auto-activation'.
Intended to be used as the `allout-auto-activation' :set function.
(fn VAR VALUE)
(defalias 'allout-auto-activation-helper #[514 "\300\"\210\301 \207" [set-default allout-setup] 5 (#$ . 5643)])
#@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 #[0 "\204 \301\302\303\"\207\304\302\303\"\207" [allout-auto-activation remove-hook find-file-hook allout-find-file-hook add-hook] 3 (#$ . 5884)])
(byte-code "\300\301\302\303\304DD\305\306\307\310\311\312\313& \210\314 \210\300\315\302\303\316DD\317\310\320\312\313&\210\321\320\322\323\310\324%\210\300\325\302\303\326DD\327\310\330\312\313&\210\331\325!\210\300\332\302\303\333DD\334\335\336\310\330\312\313& \210\331\332!\210\300\337\302\303\340DD\341\310\330\312\313&\210\331\337!\210\342\337\343\344#\210\300\345\302\303\346DD\347\310\350\312\313&\210\331\345!\210\342\345\343\351#\210\300\352\302\303\353DD\354\310\330\312\313&\210\331\352!\210\342\352\343\344#\210\300\355\302\303\356DD\357\310\330\312\313&\210\300\360\302\303\361DD\362\310\330\312\313&\210\300\363\302\303\364DD\365\310\366\312\313&\210\331\363!\210\342\363\343\367#\210\300\370\302\303\371DD\372\310\366\312\313&\210\331\370!\210\342\370\343\367#\210\300\373\302\303\374DD\375\310\366\312\313&\210\331\373!\210\342\373\343\367#\210\300\376\302\303\377DD\201@ \310\366\312\313&\210\331\376!\210\342\376\343\367#\210\300\201A \302\303\201B DD\201C \310\201D \312\313&\210\342\201A \343\201E #\207" [custom-declare-variable allout-auto-activation funcall function #[0 "\300\207" [nil] 1 #1=""] "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 #[0 "\300\207" [(-2 : 0)] 1 #1#] "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\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 #[0 "\300\207" [nil] 1 #1#] "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 #[0 "\300\207" [nil] 1 #1#] "If non-nil, auto-fill will be inhibited while on topic's header line." :version "24.1" allout-use-hanging-indents #[0 "\300\207" [t] 1 #1#] "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 booleanp allout-reindent-bodies #[0 "\205 \301\207" [allout-use-hanging-indents text] 1 #1#] "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)) #[257 "\211\300>\207" [(nil t text force)] 3 "\n\n(fn X)"] allout-show-bodies #[0 "\300\207" [nil] 1 #1#] "If non-nil, show entire body when exposing a topic, rather than just the header." allout-beginning-of-line-cycles #[0 "\300\207" [t] 1 #1#] "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 #[0 "\300\207" [t] 1 #1#] "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 #[0 "\300\207" ["."] 1 #1#] "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 #[0 "\300\207" ["*"] 1 #1#] "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 #[0 "\300\207" [".,"] 1 #1#] "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 #[0 "\300\207" ["*+-=>()[{}&!?#%\"X@$~_\\:;^"] 1 #1#] "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 `allout-set-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 #[0 "\300\207" [t] 1 #1#] "When non-nil, use mode-specific topic-header prefixes.\n\nAllout outline mode will use the mode-specific `allout-mode-leaders' or\n`comment-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\n`comment-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)) #[257 "\211\300>\206 \211;\207" [(t nil allout-mode-leaders comment-start)] 3 "\n\n(fn X)"]] 10)
#@486 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 (#$ . 20140))
(byte-code "\300\301\302\303\304DD\305\306\307\310\311&\210\312\301!\210\313\301\314\315#\210\300\316\302\303\317DD\320\306\307\310\311&\210\312\316!\210\313\316\314\315#\210\300\321\302\303\322DD\323\306\324\310\311&\210\312\321!\210\313\321\314\325#\210\300\326\302\303\327DD\330\306\331\310\311&\210\313\326\314\325#\210\300\332\302\303\333DD\334\306\335\310\311&\210\312\332!\210\313\332\314\336#\210\337\340\341\342#\210\343\211\203\241 \211@\340N\203\232 \341N\204\232 \313\341\340N#\210A\266\202\202\200 \210\344\340\341\345#\210\300\341\302\303\346DD\347\350\345\306\307\310\311& \210\300\351\302\303\352DD\353\306\307\310\311&\210\300\354\302\303\355DD\356\306\357\310\311&\210\300\360\302\303\361DD\362\306\357\310\311&\210\300\363\302\303\364DD\362\306\357\310\311&\210\300\365\302\303\366DD\367\306\357\310\311&\210\300\370\302\303\371DD\372\306\373\374\375\310\311& \210\300\376\302\303\377DD\201@ \306\357\310\311&\210\300\201A \302\303\201B DD\201C \306\357\310\311&\210\201D \201E \342\201F \310\311%\210\300\201G \302\303\201H DD\201I \306\201J \350\201K \310\201E & \210\300\201L \302\303\201M DD\201N \306\307\350\201O \310\201E & \210\312\201L !\207" [custom-declare-variable allout-old-style-prefixes funcall function #[0 "\300\207" [nil] 1 #1=""] "When non-nil, use only old-and-crusty `outline-mode' `*' topic prefixes.\n\nNon-nil restricts the topic creation and modification\nfunctions to asterix-padded prefixes, so they look exactly\nlike the original Emacs-outline style prefixes.\n\nWhatever the setting of this variable, both old and new style prefixes\nare always respected by the topic maneuvering functions." :type boolean :group allout make-variable-buffer-local put safe-local-variable booleanp allout-stylish-prefixes #[0 "\300\207" [t] 1 #1#] "Do fancy stuff with topic prefix bullets according to level, etc.\n\nNon-nil enables topic creation, modification, and repositioning\nfunctions to vary the topic bullet char (the char that marks the topic\ndepth) just preceding the start of the topic text) according to level.\nOtherwise, only asterisks (`*') and distinctive bullets are used.\n\nThis is how an outline can look (but sans indentation) with stylish\nprefixes:\n\n * Top level\n .* A topic\n . + One level 3 subtopic\n . . One level 4 subtopic\n . . A second 4 subtopic\n . + Another level 3 subtopic\n . #1 A numbered level 4 subtopic\n . #2 Another\n . ! Another level 4 subtopic with a different distinctive bullet\n . #4 And another numbered level 4 subtopic\n\nThis would be an outline with stylish prefixes inhibited (but the\nnumbered and other distinctive bullets retained):\n\n * Top level\n .* A topic\n . * One level 3 subtopic\n . * One level 4 subtopic\n . * A second 4 subtopic\n . * Another level 3 subtopic\n . #1 A numbered level 4 subtopic\n . #2 Another\n . ! Another level 4 subtopic with a different distinctive bullet\n . #4 And another numbered level 4 subtopic\n\nStylish and constant prefixes (as well as old-style prefixes) are\nalways respected by the topic maneuvering functions, regardless of\nthis variable setting.\n\nThe setting of this var is not relevant when `allout-old-style-prefixes'\nis non-nil." allout-numbered-bullet #[0 "\300\207" ["#"] 1 #1#] "String designating bullet of topics that have auto-numbering; nil for none.\n\nTopics having this bullet have automatic maintenance of a sibling\nsequence-number tacked on, just after the bullet. Conventionally set\nto \"#\", you can set it to a bullet of your choice. A nil value\ndisables numbering maintenance." (choice (const nil) string) string-or-null-p allout-file-xref-bullet #[0 "\300\207" ["@"] 1 #1#] "Bullet signifying file cross-references, for `allout-resolve-xref'.\n\nSet this var to the bullet you want to use for file cross-references." (choice (const nil) string) allout-presentation-padding #[0 "\300\207" [2] 1 #1#] "Presentation-format white-space padding factor, for greater indent." integer integerp defvaralias allout-abbreviate-flattened-numbering allout-flattened-numbering-abbreviation nil (saved-value saved-variable-comment) make-obsolete-variable "24.1" #[0 "\300\207" [nil] 1 #1#] "If non-nil, `allout-flatten-exposed-to-buffer' abbreviates topic\nnumbers to minimal amount with some context. Otherwise, entire\nnumbers are always used." :version allout-number-pages #[0 "\300\207" [nil] 1 #1#] "Non-nil turns on page numbering for LaTeX formatting of an outline." allout-label-style #[0 "\300\207" ["\\large\\bf"] 1 #1#] "Font and size of labels for LaTeX formatting of an outline." string allout-head-line-style #[0 "\300\207" ["\\large\\sl "] 1 #1#] "Font and size of entries for LaTeX formatting of an outline." allout-body-line-style #[0 "\300\207" [" "] 1 #1#] allout-title-style #[0 "\300\207" ["\\Large\\bf"] 1 #1#] "Font and size of titles for LaTeX formatting of an outline." allout-title #[0 "\300\207" [(or buffer-file-name (buffer-name))] 1 #1#] "Expression to evaluate to determine the title for LaTeX formatted copy." sexp :risky t allout-line-skip #[0 "\300\207" [".05cm"] 1 #1#] "Space between lines for LaTeX formatting of an outline." allout-indent #[0 "\300\207" [".3cm"] 1 #1#] "LaTeX formatted depth-indent spacing." custom-declare-group allout-encryption "Settings for topic encryption features of allout outliner." allout-topic-encryption-bullet #[0 "\300\207" ["~"] 1 #1#] "Bullet signifying encryption of the entry's body." (choice (const nil) string) "22.1" allout-encrypt-unencrypted-on-saves #[0 "\300\207" [t] 1 #1#] "If non-nil, topics pending encryption are encrypted during buffer saves.\n\nThis prevents file-system exposure of un-encrypted contents of\nitems marked for encryption.\n\nWhen non-nil, if the topic currently being edited is decrypted,\nit will be encrypted for saving but automatically decrypted\nbefore any subsequent user interaction, so it is once again clear\ntext for editing though the file system copy is encrypted.\n\n(Auto-saves are handled differently. Buffers with plain-text\nexposed encrypted topics are exempted from auto saves until all\nsuch topics are encrypted.)" "23.1"] 10)
#@192 Non-nil while topic encryption is pending and auto-saving was active.
The value of `buffer-saved-size' at the time of decryption is used,
for restoring when all encryptions are established.
(defvar allout-auto-save-temporarily-disabled nil (#$ . 26880))
#@71 Non-nil just after undo commands, until allout-post-command-business.
(defvar allout-just-did-undo nil (#$ . 27141))
(byte-code "\300\301!\210\302\303\304\305\306\307%\210\310\311\312\313\314DD\315\316\317\306\307&\210\300\311!\207" [make-variable-buffer-local allout-just-did-undo custom-declare-group allout-developer nil "Allout settings developers care about, including topic encryption and more." :group allout custom-declare-variable allout-enable-file-variable-adjustment funcall function #[0 "\300\207" [t] 1 ""] "If non-nil, some allout outline actions edit Emacs local file var text.\n\nThis can range from changes to existing entries, addition of new ones,\nand creation of a new local variables section when necessary.\n\nEmacs file variables adjustments are also inhibited if `enable-local-variables'\nis nil.\n\nOperations potentially causing edits include allout encryption routines.\nFor details, see `allout-toggle-current-subtree-encryption's docstring." :type boolean] 8)
#@48 Version of currently loaded allout.el package.
(defvar allout-version "2.3" (#$ . 28139))
#@75 Return string describing the loaded outline version.
(fn &optional HERE)
(defalias 'allout-version #[256 "\301P\203\n \211c\210\302\303\"\210\207" [allout-version "Allout Outline Mode v " message "%s"] 5 (#$ . 28235) "P"])
#@38 Allout outline mode minor-mode flag.
(defvar allout-mode nil (#$ . 28468))
(make-variable-buffer-local 'allout-mode)
#@1049 Buffer-specific setting for allout layout.
In buffers where this is non-nil (and if `allout-auto-activation'
has been customized to enable this behavior), `allout-mode' will be
automatically activated. The layout dictated by the value will be used to
set the initial exposure when `allout-mode' is activated.
*You should not `setq-default' this variable non-nil unless you want every
visited file to be treated as an allout file.*
The value would typically be set by a file local variable. For
example, the following lines at the bottom of an Emacs Lisp file:
;;;Local variables:
;;;allout-layout: (0 : -1 -1 0)
;;;End:
dictate activation of `allout-mode' mode when the file is visited
(presuming proper `allout-auto-activation' customization),
followed by the equivalent of `(allout-expose-topic 0 : -1 -1 0)'.
(This is the layout used for the allout.el source file.)
`allout-default-layout' describes the specification format.
`allout-layout' can additionally have the value t, in which
case the value of `allout-default-layout' is used.
(defvar allout-layout nil (#$ . 28593))
(byte-code "\300\301!\210\302\301\303\304#\207" [make-variable-buffer-local allout-layout put safe-local-variable #[257 "\211\247\206
\211<\206
\211\300>\207" [(: * + -)] 3 "\n\n(fn X)"]] 4)
#@215 Regular expression to match the beginning of a heading line.
Any line whose beginning matches this regexp is considered a
heading. This var is set according to the user configuration vars
by `allout-set-regexp'.
(defvar allout-regexp "" (#$ . 29881))
(make-variable-buffer-local 'allout-regexp)
#@247 A string dictating the valid set of outline topic bullets.
This var should *not* be set by the user -- it is set by `allout-set-regexp',
and is produced from the elements of `allout-plain-bullets-string'
and `allout-distinctive-bullets-string'.
(defvar allout-bullets-string "" (#$ . 30185))
(make-variable-buffer-local 'allout-bullets-string)
#@59 Length of current buffers' `allout-plain-bullets-string'.
(defvar allout-bullets-string-len 0 (#$ . 30536))
(make-variable-buffer-local 'allout-bullets-string-len)
#@454 Regular expression to match a heading line prefix for a particular depth.
This expression is used to search for depth-specific topic
headers at depth 2 and greater. Use `allout-depth-one-regexp'
for to seek topics at depth one.
This var is set according to the user configuration vars by
`allout-set-regexp'. It is prepared with format strings for two
decimal numbers, which should each be one less than the depth of the
topic prefix to be matched.
(defvar allout-depth-specific-regexp "" (#$ . 30707))
(make-variable-buffer-local 'allout-depth-specific-regexp)
#@289 Regular expression to match a heading line prefix for depth one.
This var is set according to the user configuration vars by
`allout-set-regexp'. It is prepared with format strings for two
decimal numbers, which should each be one less than the depth of the
topic prefix to be matched.
(defvar allout-depth-one-regexp "" (#$ . 31280))
(make-variable-buffer-local 'allout-depth-one-regexp)
#@111 `allout-regexp' prepended with a newline for the search target.
This is properly set by `allout-set-regexp'.
(defvar allout-line-boundary-regexp nil (#$ . 31678))
(make-variable-buffer-local 'allout-line-boundary-regexp)
#@73 Like `allout-line-boundary-regexp', for headers at beginning of buffer.
(defvar allout-bob-regexp nil (#$ . 31906))
(make-variable-buffer-local 'allout-bob-regexp)
#@69 Allout-header prefix length to subtract when computing topic depth.
(defvar allout-header-subtraction (byte-code "GS\207" [allout-header-prefix] 1) (#$ . 32076))
(make-variable-buffer-local 'allout-header-subtraction)
#@74 Length of `allout-plain-bullets-string', updated by `allout-set-regexp'.
(defvar allout-plain-bullets-string-len (length allout-plain-bullets-string) (#$ . 32301))
(make-variable-buffer-local 'allout-plain-bullets-string-len)
#@1272 Validate apparent topics of this depth and shallower as being non-aberrant.
Verified with `allout-aberrant-container-p'. The usefulness of
this check is limited to shallow depths, because the
determination of aberrance is according to the mistaken item
being followed by a legitimate item of excessively greater depth.
The classic example of a mistaken item, for a standard allout
outline configuration, is a body line that begins with an `...'
ellipsis. This happens to contain a legitimate depth-2 header
prefix, constituted by two `..' dots at the beginning of the
line. The only thing that can distinguish it *in principle* from
a legitimate one is if the following real header is at a depth
that is discontinuous from the depth of 2 implied by the
ellipsis, ie depth 4 or more. As the depth being tested gets
greater, the likelihood of this kind of disqualification is
lower, and the usefulness of this test is lower.
Extending the depth of the doublecheck increases the amount it is
applied, increasing the cost of the test - on casual estimation,
for outlines with many deep topics, geometrically (O(n)?).
Taken together with decreasing likelihood that the test will be
useful at greater depths, more modest doublecheck limits are more
suitably economical.
(defconst allout-doublecheck-at-and-shallower 3 (#$ . 32535))
#@76 Reset the leading string used to identify topic headers.
(fn HEADER-LEAD)
(defalias 'allout-reset-header-lead #[257 "\211\211GS\302 \207" [allout-header-prefix allout-header-subtraction allout-set-regexp] 2 (#$ . 33874) "sNew lead string: "])
#@193 Set the topic-header leading string to specified string.
Useful for encapsulating outline structure in programming
language comments. Returns the leading string.
(fn &optional HEADER-LEAD)
(defalias 'allout-lead-with-comment-string #[256 "\211;\204\n \301\302!\262\303\304!\210\207" [allout-reindent-bodies read-string "String prefix for topic headers: " nil allout-reset-header-lead] 3 (#$ . 34127) "P"])
#@326 Determine appropriate `allout-header-prefix' and `allout-primary-bullet'.
Works according to settings of:
`comment-start'
`allout-header-prefix' (default)
`allout-use-mode-specific-leader'
and `allout-mode-leaders'.
Apply this via (re)activation of `allout-mode', rather than
invoking it directly.
(defalias 'allout-infer-header-lead-and-primary-bullet #[0 "\306\300!\205 ;\204 \307>\203 \202 \310\211\204 \311\202V \211;\203'