LEFT TEXT
_library/index-include.md.cms
_library/sitemap-include.md.cms
pandoc [options] [input-file]…
Pandoc is a Haskell library for converting from one markup format to another, and a command-line tool that uses this library.
Pandoc can convert between numerous markup and word processing formats, including, but not limited to, various flavors of Markdown, HTML, LaTeX and Word docx. For the full lists of input and output formats, see the --from and --to options below. Pandoc can also produce PDF output: see creating a PDF, below.
Pandoc’s enhanced version of Markdown includes syntax for tables, definition lists, metadata blocks, footnotes, citations, math, and much more. See below under Pandoc’s Markdown.
[…]
The ideal workflow is to put [Composer] in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:
.../.Composer
.../
.../tld/
.../tld/sub/To save on disk space, using a central [Composer] install for multiple directory trees, the [init] target can be used to create a linked .Composer directory:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):
make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.ymlCustom targets can also be defined, using standard [GNU Make] syntax (see [Custom Targets]).
[…]
The ideal workflow is to put [Composer] in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:
.../.Composer
.../
.../tld/
.../tld/sub/To save on disk space, using a central [Composer] install for multiple directory trees, the [init] target can be used to create a linked .Composer directory:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):
make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.ymlCustom targets can also be defined, using standard [GNU Make] syntax (see [Custom Targets]).
[…]
The ideal workflow is to put [Composer] in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:
.../.Composer
.../
.../tld/
.../tld/sub/To save on disk space, using a central [Composer] install for multiple directory trees, the [init] target can be used to create a linked .Composer directory:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):
make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.ymlCustom targets can also be defined, using standard [GNU Make] syntax (see [Custom Targets]).
[…]
The ideal workflow is to put [Composer] in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:
.../.Composer
.../
.../tld/
.../tld/sub/To save on disk space, using a central [Composer] install for multiple directory trees, the [init] target can be used to create a linked .Composer directory:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):
make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.ymlCustom targets can also be defined, using standard [GNU Make] syntax (see [Custom Targets]).
[…]
The ideal workflow is to put [Composer] in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:
.../.Composer
.../
.../tld/
.../tld/sub/To save on disk space, using a central [Composer] install for multiple directory trees, the [init] target can be used to create a linked .Composer directory:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):
make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.ymlCustom targets can also be defined, using standard [GNU Make] syntax (see [Custom Targets]).
[…]
The ideal workflow is to put [Composer] in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:
.../.Composer
.../
.../tld/
.../tld/sub/To save on disk space, using a central [Composer] install for multiple directory trees, the [init] target can be used to create a linked .Composer directory:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):
make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.ymlCustom targets can also be defined, using standard [GNU Make] syntax (see [Custom Targets]).
[…]
The ideal workflow is to put [Composer] in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:
.../.Composer
.../
.../tld/
.../tld/sub/To save on disk space, using a central [Composer] install for multiple directory trees, the [init] target can be used to create a linked .Composer directory:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):
make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.ymlCustom targets can also be defined, using standard [GNU Make] syntax (see [Custom Targets]).
[…]
The ideal workflow is to put [Composer] in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:
.../.Composer
.../
.../tld/
.../tld/sub/To save on disk space, using a central [Composer] install for multiple directory trees, the [init] target can be used to create a linked .Composer directory:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):
make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.ymlCustom targets can also be defined, using standard [GNU Make] syntax (see [Custom Targets]).
[…]
The ideal workflow is to put [Composer] in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:
.../.Composer
.../
.../tld/
.../tld/sub/To save on disk space, using a central [Composer] install for multiple directory trees, the [init] target can be used to create a linked .Composer directory:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):
make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.ymlCustom targets can also be defined, using standard [GNU Make] syntax (see [Custom Targets]).
[…]
The ideal workflow is to put [Composer] in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:
.../.Composer
.../
.../tld/
.../tld/sub/To save on disk space, using a central [Composer] install for multiple directory trees, the [init] target can be used to create a linked .Composer directory:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):
make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.ymlCustom targets can also be defined, using standard [GNU Make] syntax (see [Custom Targets]).
[…]