%PDF- <> %âãÏÓ endobj 2 0 obj <> endobj 3 0 obj <>/ExtGState<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI] >>/Annots[ 28 0 R 29 0 R] /MediaBox[ 0 0 595.5 842.25] /Contents 4 0 R/Group<>/Tabs/S>> endobj ºaâÚÎΞ-ÌE1ÍØÄ÷{òò2ÿ ÛÖ^ÔÀá TÎ{¦?§®¥kuµùÕ5sLOšuY>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<> endobj 2 0 obj<>endobj 2 0 obj<>es 3 0 R>> endobj 2 0 obj<> ox[ 0.000000 0.000000 609.600000 935.600000]/Fi endobj 3 0 obj<> endobj 7 1 obj<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI]>>/Subtype/Form>> stream
;ELC ;;; Compiled ;;; in Emacs version 25.2.1 ;;; with all optimizations. ;;; This file contains utf-8 non-ASCII characters, ;;; and so cannot be loaded into Emacs 22 or earlier. (and (boundp 'emacs-version) (< (aref emacs-version (1- (length emacs-version))) ?A) (string-lessp emacs-version "23") (error "`%s' was compiled for Emacs 23 or later" #$)) ;;;;;;;;;;;;;;;;;;;;;;;;;;;;; (byte-code "\300\301!\210\300\302!\207" [require format-spec ox] 2) #@42 Temporary list of files to be published. (defvar org-publish-temp-files nil (#$ . 478)) #@109 This will cache timestamps and titles for files in publishing projects. Blocks could hash sha1 values here. (defvar org-publish-cache nil (#$ . 573)) (byte-code "\300\301\302\303\304\305\306\307&\210\310\311\302\312\306\313\314\315&\210\310\316\317\320\306\313\314\321&\210\310\322\323\324\306\313\314\325&\210\310\326\317\327\306\313\314\321&\210\310\330\331\332\306\313\314\333&\210\310\334\335\336\306\313\314\333&\210\310\337\302\340\306\313\314\321&\210\310\341\342\343\306\313\314\344&\210\310\345\346\347\306\313\314\344&\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,\n alternating keys and values, specifying parameters for the\n publishing process.\n\n (:property value :property value ... )\n\n2. A meta-project definition, specifying of a list of\n 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'\nare taken to be components of the project, which group together\nfiles requiring different publishing options. When you publish\nsuch a project with \\[org-publish], the components all publish.\n\nWhen a property is given a value in `org-publish-project-alist',\nits setting overrides the value of the corresponding user\nvariable (if any) during publishing. However, options set within\na file override everything.\n\nMost properties are optional, but some should always be set:\n\n `:base-directory'\n\n Directory containing publishing source files.\n\n `:base-extension'\n\n Extension (without the dot!) of source files. This can be\n a regular expression. If not given, \"org\" will be used as\n default extension.\n\n `:publishing-directory'\n\n Directory (possibly remote) where output files will be\n 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,\nthe exclusion 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\nset of output formats.\n\n `:publishing-function'\n\n Function to publish file. Each back-end may define its\n own (i.e. `org-latex-publish-to-pdf',\n `org-html-publish-to-html'). May be a list of functions, in\n which case each function in the list is invoked in turn.\n\nAnother property allows you to insert code that prepares\na project for publishing. For example, you could call GNU Make\non a certain makefile, to ensure published files are built up to\ndate.\n\n `:preparation-function'\n\n Function to be called before publishing this project. This\n may also be a list of functions.\n\n `:completion-function'\n\n Function to be called after publishing this project. This\n may also be a list 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. Back-end specific properties may also be\nincluded. See the back-end documentation for more information.\n\n :author `user-full-name'\n :creator `org-export-creator-string'\n :email `user-mail-address'\n :exclude-tags `org-export-exclude-tags'\n :headline-levels `org-export-headline-levels'\n :language `org-export-default-language'\n :preserve-breaks `org-export-preserve-breaks'\n :section-numbers `org-export-with-section-numbers'\n :select-tags `org-export-select-tags'\n :time-stamp-file `org-export-time-stamp-file'\n :with-archived-trees `org-export-with-archived-trees'\n :with-author `org-export-with-author'\n :with-creator `org-export-with-creator'\n :with-date `org-export-with-date'\n :with-drawers `org-export-with-drawers'\n :with-email `org-export-with-email'\n :with-emphasize `org-export-with-emphasize'\n :with-entities `org-export-with-entities'\n :with-fixed-width `org-export-with-fixed-width'\n :with-footnotes `org-export-with-footnotes'\n :with-inlinetasks `org-export-with-inlinetasks'\n :with-latex `org-export-with-latex'\n :with-priority `org-export-with-priority'\n :with-smart-quotes `org-export-with-smart-quotes'\n :with-special-strings `org-export-with-special-strings'\n :with-statistics-cookies' `org-export-with-statistics-cookies'\n :with-sub-superscript `org-export-with-sub-superscripts'\n :with-toc `org-export-with-toc'\n :with-tables `org-export-with-tables'\n :with-tags `org-export-with-tags'\n :with-tasks `org-export-with-tasks'\n :with-timestamps `org-export-with-timestamps'\n :with-planning `org-export-with-planning'\n :with-todo-keywords `org-export-with-todo-keywords'\n\nThe following properties may be used to control publishing of\na site-map of files or summary page for a given project.\n\n `:auto-sitemap'\n\n Whether to publish a site-map during\n `org-publish-current-project' or `org-publish-all'.\n\n `:sitemap-filename'\n\n Filename for output of sitemap. Defaults to \"sitemap.org\".\n\n `:sitemap-title'\n\n Title of site-map page. Defaults to name of file.\n\n `:sitemap-function'\n\n Plugin function to use for generation of site-map. Defaults\n to `org-publish-org-sitemap', which generates a plain list of\n links to all files in the project.\n\n `:sitemap-style'\n\n Can be `list' (site-map is just an itemized list of the\n titles of the files involved) or `tree' (the directory\n structure of the source files is reflected in the site-map).\n Defaults to `tree'.\n\n `:sitemap-sans-extension'\n\n Remove extension from site-map's file-names. Useful to have\n cool URIs (see http://www.w3.org/Provider/Style/URI).\n Defaults to nil.\n\nIf you create a site-map file, adjust the sorting like this:\n\n `:sitemap-sort-folders'\n\n Where folders should appear in the site-map. Set this to\n `first' (default) or `last' to display folders first or last,\n respectively. Any other value will mix files and folders.\n\n `:sitemap-sort-files'\n\n The site map is normally sorted alphabetically. You can\n change this behavior setting this to `anti-chronologically',\n `chronologically', or nil.\n\n `:sitemap-ignore-case'\n\n Should sorting be case-sensitive? Default nil.\n\nThe following property control the creation of a concept index.\n\n `:makeindex'\n\n Create a concept index. The file containing the index has to\n be called \"theindex.org\". If it doesn't exist in the\n project, it will be generated. Contents of the index are\n stored in the file \"theindex.inc\", which can be included in\n \"theindex.org\".\n\nOther properties affecting publication.\n\n `:body-only'\n\n Set this to t to publish only the body of the documents." org-export-publish :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-sitemap-sort-files 'alphabetically "Method to sort files in site-maps.\nPossible values are `alphabetically', `chronologically',\n`anti-chronologically' and nil.\n\nIf `alphabetically', files will be sorted alphabetically. If\n`chronologically', files will be sorted with older modification\ntime first. If `anti-chronologically', files will be sorted with\nnewer modification time first. nil won't sort files.\n\nYou can overwrite this default per project in your\n`org-publish-project-alist', using `:sitemap-sort-files'." 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 "Non-nil when site-map sorting should ignore case.\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 printing a date in the sitemap.\nSee `format-time-string' for allowed formatters." string org-publish-sitemap-file-entry-format "%t" "Format string for site-map file entry.\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'."] 8) #@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 (#$ . 10558)]) #@426 Non-nil 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) "\204 \306\202 \307 \n\f$\211\203 \310\311 #\210\202&