travs/markdown-pdf

Convert markdown to pdf, png or jpeg on the fly in Atom

Markdown to PDF

Convert markdown-formatted documents to pdf files without ever leaving Atom.

Usage

Just focus the window containing your markdown file and use the convert command (Packages > Markdown PDF > Convert).

The output PDF will be styled similar to the markdown on github.com, as well as any user styles you have added.

It will appear in the same directory as the Markdown you are converting, with the same name and a .pdf extension.

You can set parameters in the package's settings, such as page and border size.

Tips

User styles

Note that user styles will have to be encapsulated in a .markdown-body selector to override the default stylesheets, like this:

.markdown-body {
  h1 {
    font-size: 1.3em;
  }
}

Page breaks

Page breaks can be added with this element:

<div style="page-break-after: always;"></div>

Image paths

If you have trouble rendering an image, you may have to use a relative path:

# this doesn't work:
![logo](/assets/logo.png)

# but this does
![logo](./assets/logo.png)

Heart it? Hate it?

Feel free to run apm star 'markdown-pdf' or give some feedback 😄

Special thanks to these folks

• @BlueHatbRit
• @jooola
• @NKMR6194
• @Nicnl
• @brianchung808
• @hdmi
• @CumpsD
• @pydolan
• @Galadirith

markdown-pdf's Issues

Update docs

Describe using your own styles, how this package uses the active theme, and where the pdf will appear with instructions

`Convert` is not responding

I am having trouble generating any outpuf from markdown-pdf. Nothing seems to happen if the convert command is called. Not when called form the menu, neither from the keyboard shortcut.

I am using version 1.3.5 of markdown-pdf.

Workspace.Object.defineProperty.get is deprecated.

Use ::getActivePaneItem() instead of the ::activePaneItem property

Workspace.Object.defineProperty.get (/Applications/Atom.app/Contents/Resources/app.asar/src/workspace.js:892:14)
getOutputPath (/Users/julian/.atom/packages/markdown-pdf/lib/markdown-pdf.js:170:36)
atom-workspace.module.exports.convert (/Users/julian/.atom/packages/markdown-pdf/lib/markdown-pdf.js:55:17)
CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:238:29)

Uncaught TypeError: Cannot read property 'call' of undefined

From @NKMR6194 on May 20, 2015 17:5

When using markdown-pdf, v1.3.6, atom raise it.
Is reporting plugin-repo better?

Atom Version: 0.200.0
System: Mac OS X 10.10.3
Thrown From: Atom Core

Stack Trace

Uncaught TypeError: Cannot read property 'call' of undefined

At /Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:238

TypeError: Cannot read property 'call' of undefined
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:238:28)
    at CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61)
    at CommandRegistry.module.exports.CommandRegistry.dispatch (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:153:19)
    at EventEmitter.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:71:30)
    at emitOne (events.js:77:13)
    at EventEmitter.emit (events.js:166:7)

Commands

     -0:00.8.0 markdown-pdf:convert (ol.tree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)

Config

{
  "core": {
    "disabledPackages": [
      "atom-terminal",
      "language-haml",
      "web-view",
      "language-haskell",
      "language-slim",
      "japanese-wrap"
    ],
    "themes": [
      "atom-dark-ui",
      "atom-dark-syntax"
    ]
  },
  "editor": {
    "invisibles": {}
  }
}

Installed Packages

# User
markdown-pdf, v1.3.6

# Dev
No dev packages

Copied from original issue: atom/atom#6870

Render clickable links in PDF output

As @beltex said in #9, this is probably due to the way phantomjs renders the doc on osx.
Raising a new issue in case it is not.

Uncaught TypeError: Cannot read property 'split' of undefined

How to reproduce

• Create a new file
• Convert to PDF without saving the file

Uncaught TypeError: Cannot read property 'split' of undefined
/path/to/.atom/packages/markdown-pdf/lib/markdown-pdf.js:75

Supporting non-standard Markdown Previewer CSS

Issue

I use markdown-preview-plus for its excellent MathJax support (using the mathjax-wrapper to expose Atom's LaTeX library). This previewer cannot be used in conjunction with the Atom-provided markdown-preview package, so one has to be disabled for the other to be usable.

Request

Failing an official resolution, I would appreciate any guidance in solving this issue just for my personal use. I can imagine two breakpoints:

1. The prepending CSS cannot be pulled from markdown-preview
2. marked does not support Mathjax

Thanks for the awesome work and any help.

Improving markdown-pdf options.

Due to the current settings-view package issue , i guess the only workaround is to use command platte (as they told me on that open issue) which only provides the commands provided by some package like markdown-pdf , and because i really like this package i had to think about another way to avoid settings issues in the future, then i need to ask you first , what are possibilities of adding something like this to markdown-pdf ? and how it will communicate with the rest of the code ?
I tried to figure out how the markdown-pdf.js know what you selected (pdf, png or jpeg) but i couldn't.

Here is what i want to be achieved, either by you or if could help me to achieve it:

Support user styles in the output pdf?

Hello,

First of all, thanks for the great package. I really like it. But I can't figure out how how to modify the look of the output. Would I have to go into the marked package and edit the CSS there?

Apologies if this is already covered somewhere.

Thanks,
Ryan

Registering "undefined" callback

Line 50 in markdown-pdf.js should be

atom.commands.add('atom-workspace', 'markdown-pdf:convert', this.convert);

but it is:

atom.commands.add('atom-workspace', 'markdown-pdf:convert', this.convert());

This causes an error that is reported at in command-palette#42

(sorry for the formatting, I'm new to this)

User styles not working

#10 was supposed to be resolved by #11, but I have found that the following code does not give me my user style:

var user_styles = atom.styles.getStyleElements();
user_styles = user_styles[user_styles.length - 1]

Replacing the second line with user_styles = user_styles[user_styles.length - 2] does give it to me though.

This brings up an issue @schmurfy mentioned, there should be a cleaner way to get styles.

Converting an unsaved file uses the last saved version of the file

How to reproduce

• Open an .md file
• Make changes
• Convert to PDF without saving the file

one deprecation calls on Atom 194.0

I meet the following deprecation calls after just installed markdown-pdf.

Uncaught TypeError: Cannot read property 'stylesheets' of undefined

The following happens whenever I try to generate a PDF from markdown files within atom.
As it was working with the last build I used, I assume that it's related to changes in one of the last few atom releases.

---

Uncaught TypeError: Cannot read property 'stylesheets' of undefined

Atom Version: 0.158.0-9459bd1
System: linux 3.11-2-amd64
Thrown From: markdown-pdf package, v1.2.5

Steps To Reproduce

Run the PDF conversion with any markdown file

Stack Trace

At /home/stex/.atom/packages/markdown-pdf/lib/markdown-pdf.js:106

TypeError: Cannot read property 'stylesheets' of undefined
  at getStyles (/home/stex/.atom/packages/markdown-pdf/lib/markdown-pdf.js:106:29)
  at getStyledHtml (/home/stex/.atom/packages/markdown-pdf/lib/markdown-pdf.js:94:10)
  at /home/stex/.atom/packages/markdown-pdf/lib/markdown-pdf.js:65:14
  at htmlFromMd (/home/stex/.atom/packages/markdown-pdf/lib/markdown-pdf.js:88:5)
  at atom-workspace.module.exports.convert (/home/stex/.atom/packages/markdown-pdf/lib/markdown-pdf.js:63:5)
  at atom-workspace.handler (/home/stex/programs/atom/share/atom/resources/app/src/space-pen-extensions.js:115:32)
  at atom-workspace.jQuery.event.dispatch (/home/stex/programs/atom/share/atom/resources/app/node_modules/space-pen/vendor/jquery.js:4681:9)
  at atom-workspace.elemData.handle (/home/stex/programs/atom/share/atom/resources/app/node_modules/space-pen/vendor/jquery.js:4359:46)
  at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/home/stex/programs/atom/share/atom/resources/app/src/command-registry.js:243:29)
  at /home/stex/programs/atom/share/atom/resources/app/src/command-registry.js:3:61
  at CommandPaletteView.module.exports.CommandPaletteView.confirmed (/home/stex/programs/atom/share/atom/resources/app/node_modules/command-palette/lib/command-palette-view.js:120:32)
  at CommandPaletteView.module.exports.SelectListView.confirmSelection (/home/stex/programs/atom/share/atom/resources/app/node_modules/autocomplete/node_modules/atom-space-pen-views/lib/select-list-view.js:335:21)
  at space-pen-div.atom.commands.add.core:confirm (/home/stex/programs/atom/share/atom/resources/app/node_modules/autocomplete/node_modules/atom-space-pen-views/lib/select-list-view.js:109:19)
  at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/home/stex/programs/atom/share/atom/resources/app/src/command-registry.js:243:29)
  at /home/stex/programs/atom/share/atom/resources/app/src/command-registry.js:3:61
  at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/home/stex/programs/atom/share/atom/resources/app/node_modules/atom-keymap/lib/keymap-manager.js:549:16)
  at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/home/stex/programs/atom/share/atom/resources/app/node_modules/atom-keymap/lib/keymap-manager.js:391:22)
  at HTMLDocument.module.exports.WindowEventHandler.onKeydown (/home/stex/programs/atom/share/atom/resources/app/src/window-event-handler.js:167:20)

/cc @atom/core

Remove dependency on Marked

Rendering md to html is done by md-preview now, so we don't need that dependency anymore

Dark Syntax Highlighter

First of all thanks for this great plugin, it works great for me , but i have one problem with it.
the screenshot you have containing dark background at the syntax area but for me its a white background which makes some colors hard to be seen however the markdown-preview showing me a dark background.
How can i turn it into dark background to be the same as the screenshot you have in the README file, is there a specific file should be modified ?

also there is a deprecated selector

keymaps/markdown-pdf.json
Use the `atom-text-editor` tag instead of the `editor` class.

Thanks

Uncaught ReferenceError: outPath is not defined

[Enter steps to reproduce below:]

1. I didn't touch settings off the package
2. Open a .md file In left pane , markdown preview in right pane
3. focus on left pane (.md)
4. Call convert (Ctrl+Shift+C or via command palette)

Atom Version: 0.165.0
System: linux 3.17.6-1-ARCH
Thrown From: markdown-pdf package, v1.2.11

Stack Trace

Uncaught ReferenceError: outPath is not defined

At /home/dwayne/.atom/packages/markdown-pdf/lib/markdown-pdf.js:154

ReferenceError: outPath is not defined
  at processSrc (/home/dwayne/.atom/packages/markdown-pdf/lib/markdown-pdf.js:154:37)
  at convertImgSrcToURI (/home/dwayne/.atom/packages/markdown-pdf/lib/markdown-pdf.js:140:19)
  at /home/dwayne/.atom/packages/markdown-pdf/lib/markdown-pdf.js:64:14
  at htmlFromMd (/home/dwayne/.atom/packages/markdown-pdf/lib/markdown-pdf.js:88:5)
  at atom-workspace.module.exports.convert (/home/dwayne/.atom/packages/markdown-pdf/lib/markdown-pdf.js:63:5)
  at atom-workspace.handler (/usr/share/atom/resources/app/src/space-pen-extensions.js:115:32)
  at atom-workspace.jQuery.event.dispatch (/usr/share/atom/resources/app/node_modules/space-pen/vendor/jquery.js:4681:9)
  at atom-workspace.elemData.handle (/usr/share/atom/resources/app/node_modules/space-pen/vendor/jquery.js:4359:46)
  at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/usr/share/atom/resources/app/src/command-registry.js:243:29)
  at /usr/share/atom/resources/app/src/command-registry.js:3:61
  at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/usr/share/atom/resources/app/node_modules/atom-keymap/lib/keymap-manager.js:549:16)
  at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/usr/share/atom/resources/app/node_modules/atom-keymap/lib/keymap-manager.js:391:22)
  at HTMLDocument.module.exports.WindowEventHandler.onKeydown (/usr/share/atom/resources/app/src/window-event-handler.js:167:20)

Commands

     -2:17.0 command-palette:toggle (input.hidden-input)
     -2:12.3 core:confirm (input.hidden-input)
     -2:12.3 markdown-pdf:convert (input.hidden-input)
     -1:23.4 settings-view:install-packages (atom-workspace.workspace.scrollbars-visible-always.theme-atom-dark-syntax.theme-atom-dark-ui)
     -0:04.9 command-palette:toggle (input.hidden-input)
  2x -0:00.0 markdown-pdf:convert (input.hidden-input)

Config

{
  "core": {
    "disabledPackages": [
      "linter-coffeelint"
    ]
  },
  "markdown-pdf": {}
}

Installed Packages

# User
external-open, v0.3.0
git-log, v0.2.0
language-glsl, v0.2.2
language-gradle, v0.0.3
language-groovy, v0.3.0
language-protobuf, v0.2.1
linter, v0.10.0
linter-flake8, v1.2.0
linter-pylint, v0.2.0
markdown-pdf, v1.2.11
recent-projects, v0.2.6

# Dev
No dev packages

/cc @atom/core

Output .pdf contains clipboard contents

This is due to the way markdown-pdf gets the html (by copying it to the clipboard using a function in the markdown-preview main module.

I am working on a better solution for this.

Comments after export to PDF

Comments like this:

<!-- Test -->

get exported to PDF, meaning they are visible.

Support for GFMD

Support for GFMD would be fantastic, although the underlying rendered markdown-pdf may not support it.

Is it possible to change the output pdf font?

Output pdf has dejavusans font

Uncaught Error: ENOENT, open '/home/ipdfh/2_semester/AAV/Memory.md'

From @hdmi on February 22, 2015 17:0

Explanation

This error always pops up when I try to convert some Markdown file to .pdf
It might be a bug or something because I have tried the conversion y two different operate systems and always happens the same.

In both OS a new "user" folder is created out of the blue. As you can appreciate in the ENOENT appears a user ipdfh which is not mine.

• In linux the created path for the output is: '/home/ipdfh/....

• In Windows (with a totally different user from linux): C:/Users/ipdfh/....

  ---

  [Enter steps to reproduce below:]

1. ...
2. ...

Atom Version: 0.181.0
System: linux 3.13.0-45-generic
Thrown From: Atom Core

Stack Trace

Uncaught Error: ENOENT, open '/home/ipdfh/2_semester/AAV/Memory.md'

At fs.js:82

Error: ENOENT, open '/home/ipdfh/2_semester/AAV/Memory.md'
  at Error (native)

Commands

     -0:45.9 window:toggle-dev-tools (atom-text-editor.editor)
     -0:40.4 command-palette:toggle (atom-text-editor.editor)
     -0:24.8 core:confirm (atom-text-editor.editor.mini)
     -0:24.8 markdown-pdf:convert (atom-text-editor.editor)
  2x -0:14.9 core:backspace (atom-workspace.workspace.scrollbars-visible-always.theme-fizzy.theme-one-light-ui)
     -0:07.2 command-palette:toggle (atom-workspace.workspace.scrollbars-visible-always.theme-fizzy.theme-one-light-ui)
  2x -0:02.1 core:backspace (atom-text-editor.editor.mini)
     -0:00.9 core:confirm (atom-text-editor.editor.mini)
     -0:00.9 markdown-pdf:convert (atom-workspace.workspace.scrollbars-visible-always.theme-fizzy.theme-one-light-ui)

Config

{
  "core": {
    "themes": [
      "one-light-ui",
      "fizzy"
    ]
  },
  "editor": {
    "invisibles": {},
    "fontSize": 19
  }
}

Installed Packages

# User
autocomplete-paths, v1.0.2
autocomplete-plus, v2.2.0
color-picker, v1.4.4
file-icons, v1.4.11
fizzy, v0.15.0
linter, v0.11.1
linter-csslint, v0.0.11
linter-jshint, v0.1.0
linter-php, v0.0.11
markdown-format, v2.5.0
markdown-pdf, v1.3.3
pdf-view, v0.17.0

# Dev
No dev packages

Copied from original issue: atom/atom#5680

Reduce output fiesize

Woah! Didn't realize that the output .pdf is so huge!

5,6 MB for 10 pages (text only).
9,4 MB for 14 pages (text only).

What's up with that? It would be really cool if this issue is fixed, because I really like the idea of markdown -> pdf. :)

"Phatom.js script did not exit"

Trying to generate a pdf, and keep getting this error:

Error: html-pdf: PDF generation timeout. Phantom.js script did not exit.
If the error is a timeout, try running the command again. c:\Users\Harsh\.atom\packages\markdown-pdf\lib\markdown-pdf.js:120
Converted successfully. Output in c:\Users\Harsh\Desktop\Readme.pdf 

I have tried running the command several times, but still keep getting this error.

I can't actually open the .pdf it generates. Please excuse me if its a trivial problem - I am new to using atom. I also installed html-pdf and phantomjs mpm packages because for some reason I thought they were needed/the console was saying I was missing phantom.js

Thanks in advance.

Code block in PDF has a scroll bar

This is a picture of the actual PDF... and sadly, the scrollbar is not interactive 😃

Where the converted PDF will be stored?

Thank you for your plugin. But I can not find where the converted file has been saved. Can you please check this issue ?

Cross-OS Keybindings

This should be easy enough to implement, and there should be keybindings for non-OSX systems within the next few days (other tasks are taking priority).

add user style

This is a really nice plugin but one thing missing is to pull ~/.atom/styles.less into the generated html file to have the same result as shown in the preview pane.

Markdown links don't work in PDF

I have a lot of links in my document that work fine as MD and HTML, but they are dead (i.e., unclicklable) in the outputted PDF. It would be great if the links worked in the PDF as they do in HTML. Or, failing that, strip them when they're converted to PDF--though that's less desirable.

Thanks,
Ryan

image is missing in exported pdf file

for example:

![](https://assets-cdn.github.com/images/modules/logos_page/GitHub-Mark.png)

Uncaught Error: ENOENT, open 'c:\devel\tools\cpdfer\Readme.md'

From @baskinomics on February 4, 2015 5:43

[Enter steps to reproduce below:]

1. ...
2. ...

Atom Version: 0.176.0
System: Microsoft Windows 7 Professional
Thrown From: Atom Core

Stack Trace

Uncaught Error: ENOENT, open 'c:\devel\tools\cpdfer\Readme.md'

At fs.js:75

Error: ENOENT, open 'c:\devel\tools\cpdfer\Readme.md'
  at Error (native)

Commands

     -0:24.5 command-palette:toggle (atom-text-editor.editor.is-focused)
     -0:17.5 core:confirm (atom-text-editor.editor.mini)
     -0:17.4 markdown-pdf:convert (atom-text-editor.editor.is-focused)
     -0:12.4 core:move-down (atom-text-editor.editor.is-focused)

Config

{
  "core": {
    "themes": [
      "atom-dark-ui",
      "atom-dark-syntax"
    ]
  },
  "editor": {
    "fontSize": 14,
    "invisibles": {}
  }
}

Installed Packages

# User
color-picker, v1.4.4
markdown-pdf, v1.3.2

# Dev
No dev packages

Copied from original issue: atom/atom#5391

The 'Convert' button doesn't work

Because of the GFW, the apm can't install the packages. I download it from your GitHub and move it to the ~/.atom/packages. It doesn't work when I click the covert button.
OS : Yosemite 10.10.3
Atom: 187

Enable selectable text in PDF output on OS X

This is due to the way PhantomJS renders the PDF, but is not a problem on other operating systems apparently.

Since this is out of our direct control, we can wait until the feature is supported, then just update the dependency.

The issue is being tracked here.

Error: ENOENT, no such file or directory

User stylesheet may not exist (mine doesn't), so a warning should be thrown, but it should still convert.

Package.getActivationCommands is deprecated.

Use activationCommands instead of activationEvents in your package.json
Commands should be grouped by selector as follows:

  "activationCommands": {
    "atom-workspace": ["foo:bar", "foo:baz"],
    "atom-text-editor": ["foo:quux"]
  }

Package.getActivationCommands (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:808:9)
Package.hasActivationCommands (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:733:20)
<unknown> (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:185:24)
Package.measure (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:163:15)
Package.load (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:177:12)
PackageManager.loadPackage (/Applications/Atom.app/Contents/Resources/app.asar/src/package-manager.js:355:14)

Uncaught ReferenceError: outPath is not defined

Updates Atom and got this.

Working on a fix.

Settings page not working correctly

I have a wired problem, settings page not working correctly and i tired to remove the package and install it again but nothing happens. i don't know what to do.

the converter is working but the settings page is not. if i would like to convert to png , i have to type it inside not select-able like it was.

Covert command not found & key shortcut doesn't work!

Hi.
I'm new to Atom so may be missing something but I can't seem to find a command anywhere on the pull-down menu's or context menu so went into the package settings and found the keyboard shortcut and found:

Keystroke Command Selector
ctrl-alt-cmd-c markdown-pdf:convert .editor

But this doesn't seem to work for me neither. I'm using Mac OS X Yosemite.

Cheers,

P

adding custom css file inside markdown file

is there a way to use css and make it printable ?

it works in markdown-preview but when i print it i got error while converting
I know you cannot use markdown inside a div.
if i created a custom css file and give additional css to

.mardown-preview: {
background-image: url(https://octodex.github.com/images/gobbleotron.gif);
 } 

then include it inside my markdown it will fail when converting like the screenshot below.

it only works if i modified mardown-preview.less itself.

Deprecated calls / selector

The deprecation cop reports that atom.workspaceView is outdated but used in the add in. Furthermore the cop reports deprecated selectors.

Add in is still functional despite the warnings/errors

Put atom package dependencies in code

This package depends on markdown-preview and tree-view, and some people may have atom, but neither of these packages.

To make sure those packages are installed, I will be implementing something very soon.

It simply doesn't work

Atom version 0.169.0
Environment
Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz - 8Gb RAM
OpenSuSE 13.2 (kernel 3.16.7-7-desktop) x86_64
Qt: 4.8.6 KDE: 4.14.3
Python version 2.7.8

Atom plugin tree-view and preview available, clicking the convert command from the Packages->Markdown to PDF having an active MD file opened and focused doesn't trigger anything, it is just like doing nothing.

Listing the FS where the MD file is located, not PDF file is present

The plugin has been installed using the install command from the Atom settings menu

"PDF creation timeout. PDF generation script did not end."

On Windows 7:

When trying to convert the welcome.md that comes with Atom to .pdf I get a: "PDF creation timeout. PDF generation script did not end." in the console and no pdf.

Error: PDF creation timeout. PDF generation script did not end.message: "PDF creation timeout. PDF generation script did not end."stack: (...)get stack: function () { [native code] }set stack: function () { [native code] }__proto__: d c:\Users\nlriekos\.atom\packages\markdown-pdf\lib\markdown-pdf.js:78

Output .pdf styling is off

There are some issues at current with output pdf formatting incorrectly. Most notably, hyperlinks are improperly rendered.

This issue should be solved by implementing a more basic conversion tool that takes raw html to pdf instead of inline html in a markdown.

Issue with Base16-syntax theme installed

At line 150:
https://github.com/travs/markdown-pdf/blob/master/lib/markdown-pdf.js#L150

When you have the base16 syntax theme (https://atom.io/themes/base16-syntax) installed, the stylesheets array is empty and the package fails silently. I get this stack trace:

"TypeError: Cannot read property '1' of undefined
  at getStyles (/Users/bchung/.atom/packages/markdown-pdf/lib/markdown-pdf.js:150:66)
 ...

I can only reproduce it with this theme (although I only tested monokai-theme which works fine).

Just a heads up to anyone using base16-syntax theme.

Not responding to font size changes

First of all, I'd like to thank you for the great package. It's wonderful to go from markdown editing to a pdf output in a single command.

One small issue, though, is that font size in the generated pdf file is very tiny. I tried changing font sizes in the settings tab of both the editor and the package, but there is no change. It is responding to theme changes, so I'm not sure what the problem is. (I'm new to atom, so I might be missing something completely obvious.)

Generated PDF not highlighting syntax

The generated PDF's aren't including any syntax highlighting. My code sample is C#, I tried both cs and csharp.

Test

 public class FooClass
 {
     public void FooMethod(FooParameter p)
     {
         Console.WriteLine(p);
     }
 }

Respect Github Style Option

By now, markdown-preview supports GitHub style markdown rendering. While markdown-pdf respects the current Atom theme, it does not so with the new markdown-preview option concerning GitHub style.

Error when selecting from file-tree

When I click on a markdown file in the file-tree it opens in an editor and I can run convert on it.

If I do these two things in succession, it throws an error like in #14.

Should add a check to make sure file-tree isn't selected or something like that.

Options passing to html-pdf

markdown-pdf supports a number of pre-process options that would be wonderful to pass through. An example would be setting border sizes.