Server IP : 111.118.215.189 / Your IP : 18.117.158.174 Web Server : Apache System : Linux md-in-83.webhostbox.net 4.19.286-203.ELK.el7.x86_64 #1 SMP Wed Jun 14 04:33:55 CDT 2023 x86_64 User : a1673wkz ( 2475) PHP Version : 8.2.25 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON Directory (0755) : /usr/share/emacs/24.3/lisp/org/ |
[ Home ] | [ C0mmand ] | [ Upload File ] |
---|
;ELC ;;; Compiled by mockbuild@buildfarm06-new.corp.cloudlinux.com on Fri Oct 11 10:07:57 2024 ;;; from file /builddir/build/BUILD/emacs-24.3/lisp/org/org-publish.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\300\302!\210\300\303!\210\304\305!\204 \306\305\307\310B\"\210\300\207" [require org org-exp format-spec fboundp declare-function defalias macro #[(fn file &optional arglist fileonly) "\300\207" [nil] 1]] 4) #@48 The buffer `org-publish' has been called from. (defvar org-publish-initial-buffer nil (#$ . 793)) #@42 Temporary list of files to be published. (defvar org-publish-temp-files nil (#$ . 897)) #@109 This will cache timestamps and titles for files in publishing projects. Blocks could hash sha1 values here. (defvar org-publish-cache nil (#$ . 992)) (byte-code "\300\301\302\303\304\305\306\307&\210\310\311\302\312\306\301\313\314&\210\310\315\316\317\306\301\313\320&\210\310\321\322\323\306\301\313\324&\210\310\325\316\326\306\301\313\320&\210\310\327\302\330\306\301\313\331&\210\310\332\302\333\306\301\313\331&\210\310\334\335\336\306\301\337\340\313\341& \210\310\342\343\344\306\301\337\340\313\341& \210\310\345\302\346\306\301\337\340\313\320& \210\310\347\350\351\306\301\337\340\313\352& \210\310\353\354\355\306\301\337\340\313\352& \207" [custom-declare-group org-publish nil "Options for publishing a set of Org-mode and related files." :tag "Org Publishing" :group org custom-declare-variable org-publish-project-alist "Association list to control publishing behavior.\nEach element of the alist is a publishing 'project.' The CAR of\neach element is a string, uniquely identifying the project. The\nCDR of each element is in one of the following forms:\n\n1. A well-formed property list with an even number of elements, alternating\n keys and values, specifying parameters for the publishing process.\n\n (:property value :property value ... )\n\n2. A meta-project definition, specifying of a list of sub-projects:\n\n (:components (\"project-1\" \"project-2\" ...))\n\nWhen the CDR of an element of org-publish-project-alist is in\nthis second form, the elements of the list after :components are\ntaken to be components of the project, which group together files\nrequiring different publishing options. When you publish such a\nproject with \\[org-publish], the components all publish.\n\nWhen a property is given a value in org-publish-project-alist, its\nsetting overrides the value of the corresponding user variable\n(if any) during publishing. However, options set within a file\noverride everything.\n\nMost properties are optional, but some should always be set:\n\n :base-directory Directory containing publishing source files\n :base-extension Extension (without the dot!) of source files.\n This can be a regular expression. If not given,\n \"org\" will be used as default extension.\n :publishing-directory Directory (possibly remote) where output\n files will be published\n\nThe :exclude property may be used to prevent certain files from\nbeing published. Its value may be a string or regexp matching\nfile names you don't want to be published.\n\nThe :include property may be used to include extra files. Its\nvalue may be a list of filenames to include. The filenames are\nconsidered relative to the base directory.\n\nWhen both :include and :exclude properties are given values, the\nexclusion step happens first.\n\nOne special property controls which back-end function to use for\npublishing files in the project. This can be used to extend the\nset of file types publishable by org-publish, as well as the set\nof output formats.\n\n :publishing-function Function to publish file. The default is\n `org-publish-org-to-html', but other\n values are possible. May also be a\n list of functions, in which case\n each function in the list is invoked\n in turn.\n\nAnother property allows you to insert code that prepares a\nproject for publishing. For example, you could call GNU Make on a\ncertain makefile, to ensure published files are built up to date.\n\n :preparation-function Function to be called before publishing\n this project. This may also be a list\n of functions.\n :completion-function Function to be called after publishing\n this project. This may also be a list\n of functions.\n\nSome properties control details of the Org publishing process,\nand are equivalent to the corresponding user variables listed in\nthe right column. See the documentation for those variables to\nlearn more about their use and default values.\n\n :language `org-export-default-language'\n :headline-levels `org-export-headline-levels'\n :section-numbers `org-export-with-section-numbers'\n :table-of-contents `org-export-with-toc'\n :emphasize `org-export-with-emphasize'\n :sub-superscript `org-export-with-sub-superscripts'\n :TeX-macros `org-export-with-TeX-macros'\n :fixed-width `org-export-with-fixed-width'\n :tables `org-export-with-tables'\n :table-auto-headline `org-export-highlight-first-table-line'\n :style `org-export-html-style'\n :convert-org-links `org-export-html-link-org-files-as-html'\n :inline-images `org-export-html-inline-images'\n :expand-quoted-html `org-export-html-expand'\n :timestamp `org-export-html-with-timestamp'\n :publishing-directory `org-export-publishing-directory'\n :html-preamble `org-export-html-preamble'\n :html-postamble `org-export-html-postamble'\n :author `user-full-name'\n :email `user-mail-address'\n\nThe following properties may be used to control publishing of a\nsitemap of files or summary page for a given project.\n\n :auto-sitemap Whether to publish a sitemap during\n `org-publish-current-project' or `org-publish-all'.\n :sitemap-filename Filename for output of sitemap. Defaults\n to 'sitemap.org' (which becomes 'sitemap.html').\n :sitemap-title Title of sitemap page. Defaults to name of file.\n :sitemap-function Plugin function to use for generation of sitemap.\n Defaults to `org-publish-org-sitemap', which\n generates a plain list of links to all files\n in the project.\n :sitemap-style Can be `list' (sitemap is just an itemized list\n of the titles of the files involved) or\n `tree' (the directory structure of the source\n files is reflected in the sitemap). Defaults to\n `tree'.\n :sitemap-sans-extension Remove extension from sitemap's\n filenames. Useful to have cool\n URIs (see\n http://www.w3.org/Provider/Style/URI).\n Defaults to nil.\n\n If you create a sitemap file, adjust the sorting like this:\n\n :sitemap-sort-folders Where folders should appear in the sitemap.\n Set this to `first' (default) or `last' to\n display folders first or last, respectively.\n Any other value will mix files and folders.\n :sitemap-sort-files The site map is normally sorted alphabetically.\n You can change this behaviour setting this to\n `chronologically', `anti-chronologically' or nil.\n :sitemap-ignore-case Should sorting be case-sensitive? Default nil.\n\nThe following properties control the creation of a concept index.\n\n :makeindex Create a concept index.\n\nOther properties affecting publication.\n\n :body-only Set this to 't' to publish only the body of the\n documents, excluding everything outside and\n including the <body> tags in HTML, or\n egin{document}..nd{document} in LaTeX." :type alist org-publish-use-timestamps-flag t "Non-nil means use timestamp checking to publish only changed files.\nWhen nil, do no timestamp checking and always publish all files." boolean org-publish-timestamp-directory (convert-standard-filename "~/.org-timestamps/") "Name of directory in which to store publishing timestamps." directory org-publish-list-skipped-files "Non-nil means show message about files *not* published." org-publish-before-export-hook "Hook run before export on the Org file.\nThe hook may modify the file in arbitrary ways before publishing happens.\nThe original version of the buffer will be restored after publishing." hook org-publish-after-export-hook "Hook run after export on the exported buffer.\nAny changes made by this hook will be saved." org-publish-sitemap-sort-files 'alphabetically "How sitemaps files should be sorted by default?\nPossible values are `alphabetically', `chronologically', `anti-chronologically' and nil.\nIf `alphabetically', files will be sorted alphabetically.\nIf `chronologically', files will be sorted with older modification time first.\nIf `anti-chronologically', files will be sorted with newer modification time first.\nnil won't sort files.\n\nYou can overwrite this default per project in your\n`org-publish-project-alist', using `:sitemap-sort-files'." :version "24.1" symbol org-publish-sitemap-sort-folders 'first "A symbol, denoting if folders are sorted first in sitemaps.\nPossible values are `first', `last', and nil.\nIf `first', folders will be sorted before files.\nIf `last', folders are sorted to the end after the files.\nAny other value will not mix files and folders.\n\nYou can overwrite this default per project in your\n`org-publish-project-alist', using `:sitemap-sort-folders'." org-publish-sitemap-sort-ignore-case "Sort sitemaps case insensitively by default?\n\nYou can overwrite this default per project in your\n`org-publish-project-alist', using `:sitemap-ignore-case'." org-publish-sitemap-date-format "%Y-%m-%d" "Format for `format-time-string' which is used to print a date\nin the sitemap." string org-publish-sitemap-file-entry-format "%t" "How a sitemap file entry is formatted.\nYou could use brackets to delimit on what part the link will be.\n\n%t is the title.\n%a is the author.\n%d is the date formatted using `org-publish-sitemap-date-format'."] 10) (defalias 'org-publish-sanitize-plist #[(plist) "\301\302\"\207" [plist mapcar #[(x) "\301\236A\206 \207" [x ((:index-filename . :sitemap-filename) (:index-title . :sitemap-title) (:index-function . :sitemap-function) (:index-style . :sitemap-style) (:auto-index . :auto-sitemap))] 2]] 3]) #@54 Return path to timestamp file for filename FILENAME. (defalias 'org-publish-timestamp-filename #[(filename &optional pub-dir pub-func) "\303 \206 \304\303\305\306\n\206 \304\"\260\307\310\311!\203 \311!\202# \312!P\207" [filename pub-dir pub-func "::" "" format "%s" "X" fboundp sha1 md5] 7 (#$ . 11436)]) #@428 Return t if FILENAME should be published in PUB-DIR using PUB-FUNC. TRUE-PUB-DIR is where the file will truly end up. Currently we are not using this - maybe it can eventually be used to check if the file is present at the target location, and how old it is. Right now we cannot do this, because we do not know under what file name the file will be stored - the publishing function can still decide about that independently. (defalias 'org-publish-needed-p #[(filename &optional pub-dir pub-func true-pub-dir base-dir) "\203 \306 \n\f$\202 \307\211\203 \310\311 #\210\202&