LaTeX. If no output file is specified (so that output goes to stdout), or if the output file’s extension is unknown, the output format will default to HTML. If no input file is specified (so that input option. 4 Creating a PDF Creating a PDF To produce a PDF, specify an output file with a .pdf extension: pandoc test.txt -o test.pdf By default, pandoc will use LaTeX to create the PDF, which requires ConTeXt, roff ms, or HTML as an intermediate format. To do this, specify an output file with a .pdf extension, as before, but add the --pdf-engine option or -t context, -t html, or -t ms to the command line

resources on creating and distributing packages Example - Server extension Example - Server extension and nbextension Example - Bundler extension Extending the Notebook Contents API File save hooks Custom documents are internally JSON [http://en.wikipedia.org/wiki/JSON] files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled and shared with colleagues. directly, bypassing the dashboard, with jupyter notebook my_notebook.ipynb. The .ipynb extension is assumed if no extension is given. When you are inside an open notebook, the File | Open… menu option will

resources on creating and distributing packages Example - Server extension Example - Server extension and nbextension Example - Bundler extension Extending the Notebook Contents API File save hooks Custom documents are internally JSON [http://en.wikipedia.org/wiki/JSON] files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled and shared with colleagues. directly, bypassing the dashboard, with jupyter notebook my_notebook.ipynb. The .ipynb extension is assumed if no extension is given. When you are inside an open notebook, the File | Open… menu option will

representations of resulting objects. These documents are internally JSON files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled and shared with colleagues. directly, bypassing the dashboard, with jupyter notebook my_notebook.ipynb. The .ipynb extension is assumed if no extension is given. When you are inside an open notebook, the File | Open... menu option will can either be specified in a requirejs module, or registered in a registry, for example when an extension is loaded. This example shows a frontend comm target registered in a registry: Jupyter.notebook

representations of resulting objects. These documents are internally JSON files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled and shared with colleagues. directly, bypassing the dashboard, with jupyter notebook my_notebook.ipynb. The .ipynb extension is assumed if no extension is given. When you are inside an open notebook, the File | Open... menu option will on your computer, notebook documents are just files on your local filesystem with a ‘‘.ipynb‘‘ extension. This allows you to use familiar workflows for organizing your notebooks into folders and sharing

resources on creating and distributing packages Example - Server extension Example - Server extension and nbextension Example - Bundler extension Extending the Notebook Contents API File save hooks Custom documents are internally JSON [https://en.wikipedia.org/wiki/JSON] files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled and shared with colleagues. directly, bypassing the dashboard, with jupyter notebook my_notebook.ipynb. The .ipynb extension is assumed if no extension is given. When you are inside an open notebook, the File | Open… menu option will

representations of resulting objects. These documents are internally JSON files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled and shared with colleagues. directly, bypassing the dashboard, with jupyter notebook my_notebook.ipynb. The .ipynb extension is assumed if no extension is given. When you are inside an open notebook, the File | Open... menu option will can either be specified in a requirejs module, or registered in a registry, for example when an extension is loaded. This example shows a frontend comm target registered in a registry: Jupyter.notebook

representations of resulting objects. These documents are internally JSON files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled and shared with colleagues. directly, bypassing the dashboard, with jupyter notebook my_notebook.ipynb. The .ipynb extension is assumed if no extension is given. When you are inside an open notebook, the File | Open... menu option will can either be specified in a requirejs module, or registered in a registry, for example when an extension is loaded. This example shows a frontend comm target registered in a registry: Jupyter.notebook

representations of resulting objects. These documents are internally JSON files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled and shared with colleagues. directly, bypassing the dashboard, with jupyter notebook my_notebook.ipynb. The .ipynb extension is assumed if no extension is given. When you are inside an open notebook, the File | Open... menu option will can either be specified in a requirejs module, or registered in a registry, for example when an extension is loaded. This example shows a frontend comm target registered in a registry: Jupyter.notebook

representations of resulting objects. These documents are internally JSON files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled and shared with colleagues. directly, bypassing the dashboard, with jupyter notebook my_notebook.ipynb. The .ipynb extension is assumed if no extension is given. When you are inside an open notebook, the File | Open... menu option will on your computer, notebook documents are just files on your local filesystem with a ‘‘.ipynb‘‘ extension. This allows you to use familiar workflows for organizing your notebooks into folders and sharing