search

yzane / vscode-markdown-pdf

Markdown converter for Visual Studio Code
https://marketplace.visualstudio.com/items?itemName=yzane.markdown-pdf
Other
1.01k stars 205 forks source link

Markdown PDF commands not available in Command Palette. #113

Open mjsaims opened 5 years ago

mjsaims commented 5 years ago

Problem When I open a markdown file in VSCode, I used to be able to simply hit F1 (to open the Command Palette) and then type "pdf" and hit enter (which would execute the markdown-pdf: Export (pdf) command from your extension).

I've only noticed for the past week or so (don't know when it actually started)... none of your Commands are available in the Command Palette initially.

WorkAround I found a reproducible pattern: If I open the Extensions tab in VSCode, search for the Markdown PDF extension, and then click it to open the page for the extension, the commands will be made available in the Command Palette.

markdown-pdf-commands

My Environment:

OS Version: Microsoft Windows [Version 10.0.17134.345]

VSCode Version: PS C:\temp> code --version 1.30.1 dea8705087adb1b5e5ae1d9123278e178656186a ia32

Markdown PDF Extension Version: PS C:\temp> code --list-extensions --show-versions ... yzane.markdown-pdf@1.2.0 ...

VictoriousRaptor commented 5 years ago

Encoutered the same issue, and thanks for your workaroud!

lizr2004 commented 5 years ago

same issue on linux, without any settings for markdown-pdf

tfukumori commented 5 years ago

same issue on context menu. solved by workaround.

it’s happen excel viewer too.

ttupper92618 commented 5 years ago

I'm having the same issue on MacOS. The workaround does not work.

mjsaims commented 5 years ago

I recently updated VS Code to v1.31.0 and the problem seems to have gone away. The Markdown PDF commands are available in the Command Palette when I open any markdown file.

NOTE: If you have focus on the markdown preview (as opposed to the actual markdown document itself), the commands will not show up in the Palette (which is understandable).

sheeeng commented 5 years ago

I thought I have the same problem.

However, I found out that the filename had prepended and appended space characters.

I removed the the unnecessary space characters around the filename and it works!

~  uname
Darwin
~  code --version
1.37.1
f06011ac164ae4dc8e753a3fe7f9549844d15e35
x64
~  code --list-extensions --show-versions | grep yzane
yzane.markdown-pdf@1.2.0