;ELC ;;; Compiled ;;; in Emacs version 29.4 ;;; with all optimizations. (byte-code "\300\301!\210\302 \303\232\204\304\305\306\"\210\300\307!\210\310\311\312\313\314\315\316\317&\210\320\321\322\323\324DD\325\326\327\330\331&\207" [require org-macs org-release "9.6.15" warn "Org version mismatch.\nThis warning usually appears when a built-in Org version is loaded\nprior to the more recent Org version.\n\nVersion mismatch is commonly encountered in the following situations:\n\n1. Emacs is loaded using literate Org config and more recent Org\n version is loaded inside the file loaded by `org-babel-load-file'.\n `org-babel-load-file' triggers the built-in Org version clashing\n the newer Org version attempt to be loaded later.\n\n It is recommended to move the Org loading code before the\n `org-babel-load-file' call.\n\n2. New Org version is loaded manually by setting `load-path', but some\n other package depending on Org is loaded before the `load-path' is\n configured.\n This \"other package\" is triggering built-in Org version, again\n causing the version mismatch.\n\n It is recommended to set `load-path' as early in the config as\n possible.\n\n3. New Org version is loaded using straight.el package manager and\n other package depending on Org is loaded before straight triggers\n loading of the newer Org version.\n\n It is recommended to put\n\n %s\n\n early in the config. Ideally, right after the straight.el\n bootstrap. Moving `use-package' :straight declaration may not be\n sufficient if the corresponding `use-package' statement is\n deferring the loading.\n\n4. A new Org version is synchronized with Emacs git repository and\n stale .elc files are still left from the previous build.\n\n It is recommended to remove .elc files from lisp/org directory and\n re-compile." "(straight-use-package 'org)" ol org-link-set-parameters "man" :follow org-man-open :export org-man-export :store org-man-store-link custom-declare-variable org-man-command funcall function #[0 "\300\207" [man] 1 ""] "The Emacs command to be used to display a man page." :group org-link :type (choice (const man) (const woman))] 8)#@199 Visit the manpage on PATH. PATH should be a topic that can be thrown at the man command. If PATH contains extra ::STRING which will use `occur' to search matched strings in man buffer. (fn PATH _) (defalias 'org-man-open #[514 "\301\302\"\210\303\304\"\303\305\"!\205Pr\211q\210eb\210\306\307\310#\204;\311!\312!\2033\313!\210\202&\210eb\210\306!\210\314y\210`\315!\316\"\210\317\")\262\262\207" [org-man-command string-match "\\(.*?\\)\\(?:::\\(.*\\)\\)?$" match-string 1 2 search-forward nil t get-buffer-process process-live-p accept-process-output -1 get-buffer-window set-window-point set-window-start] 10 (#$ . 2196)])#@32 Store a link to a README file. (defalias 'org-man-store-link #[0 "\301>\205\302 \303P\304\305\"\306\307\310\311\312&\266\203\207" [major-mode (Man-mode woman-mode) org-man-get-page-name "man:" format "Manpage for %s" org-link-store-props :type "man" :link :description] 10 (#$ . 2849)])#@45 Extract the page name from the buffer name. (defalias 'org-man-get-page-name #[0 "\300\301\302 \"\203\303\304\302 \"\207\305\306!\207" [string-match " \\(\\S-+\\)\\*" buffer-name match-string 1 error "Cannot create link to this man page"] 3 (#$ . 3150)])#@70 Export a man page link from Org files. (fn LINK DESCRIPTION FORMAT) (defalias 'org-man-export #[771 "\300\301\"\206 \302\267\202-\300\303#\207\300\304#\207\300\305#\207\300\306#\207\300\307#\207\207" [format "http://man.he.net/?topic=%s§ion=all" #s(hash-table size 5 test eq rehash-size 1.5 rehash-threshold 0.8125 purecopy t data (html 15 latex 21 texinfo 27 ascii 33 md 39)) "%s" "\\href{%s}{%s}" "@uref{%s,%s}" "%s (%s)" "[%s](%s)"] 9 (#$ . 3412)]) (provide 'ol-man)