|
24 |
(byte-code "\300\301\302\303\304\305\306\307&\210\310\311\312\313\314DD\315\306\301\316\317&\210\310\320\312\313\321DD\322\306\301\316\323&\210\310\324\312\313\325DD\326\306\301\316\327&\210\310\330\312\313\331DD\332\306\301\316\323&\210\310\333\312\313\334DD\335\306\301\316\336&\210\310\337\312\313\340DD\341\306\301\316\342\343\344\345\346\347\350&
\210\310\351\312\313\352DD\353\306\301\316\323&\207" [custom-declare-group org-export-publish nil "Options for publishing a set of files." :tag "Org Publishing" :group org-export custom-declare-variable org-publish-project-alist funcall function #[0 "\300\207" [nil] 1] "Association list to control publishing behavior.\n\\<org-mode-map>\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. If it is `any', include all the files,\n even without extension.\n\n `:publishing-directory'\n\n Directory (possibly remote) where output files will be\n published.\n\nIf `:recursive' is non-nil files in sub-directories of\n`:base-directory' are considered.\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. Preparation functions are\n called with the project properties list as their sole\n argument.\n\n `:completion-function'\n\n Function to be called after publishing this project. This\n may also be a list of functions. Completion functions are\n called with the project properties list as their sole\n argument.\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-planning `org-export-with-planning'\n :with-priority `org-export-with-priority'\n :with-properties `org-export-with-properties'\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-title `org-export-with-title'\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 site-map. Defaults to \"sitemap.org\".\n\n `:sitemap-title'\n\n Title of site-map page. Defaults to name of file.\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-format-entry'\n\n Plugin function used to format entries in the site-map. It\n is called with three arguments: the file or directory name\n relative to base directory, the site map style and the\n current project. It has to return a string.\n\n Defaults to `org-publish-sitemap-default-entry', which turns\n file names into links and use document titles as\n descriptions. For specific formatting needs, one can use\n `org-publish-find-date', `org-publish-find-title' and\n `org-publish-find-property', to retrieve additional\n information about published documents.\n\n `:sitemap-function'\n\n Plugin function to use for generation of site-map. It is\n called with two arguments: the title of the site-map, as\n a string, and a representation of the files involved in the\n project, as returned by `org-list-to-lisp'. The latter can\n further be transformed using `org-list-to-generic',\n `org-list-to-subtree' and alike. It has to return a string.\n\n Defaults to `org-publish-sitemap-default', which generates\n a plain list of links to all files in the project.\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' or `last' to display folders first or last,\n respectively. When set to `ignore' (default), folders are\n ignored altogether. Any other value will mix files and\n folders. This variable has no effect when site-map style is\n `tree'.\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." :type alist org-publish-use-timestamps-flag #[0 "\300\207" [t] 1] "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 #[0 "\300\301!\207" [convert-standard-filename "~/.org-timestamps/"] 2] "Name of directory in which to store publishing timestamps." directory org-publish-list-skipped-files #[0 "\300\207" [t] 1] "Non-nil means show message about files *not* published." org-publish-sitemap-sort-files #[0 "\300\207" [alphabetically] 1] "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 #[0 "\300\207" [ignore] 1] "A symbol, denoting if folders are sorted first in site-maps.\n\nPossible values are `first', `last', `ignore' and nil.\nIf `first', folders will be sorted before files.\nIf `last', folders are sorted to the end after the files.\nIf `ignore', folders do not appear in the site-map.\nAny other value will mix files and folders.\n\nYou can overwrite this default per project in your\n`org-publish-project-alist', using `:sitemap-sort-folders'.\n\nThis variable is ignored when site-map style is `tree'." (choice (const :tag "Folders before files" first) (const :tag "Folders after files" last) (const :tag "No folder in site-map" ignore) (const :tag "Mix folders and files" nil)) :version "26.1" :package-version (Org . "9.1") :safe symbolp org-publish-sitemap-sort-ignore-case #[0 "\300\207" [nil] 1] "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'."] 14) |