search

qjebbs / vscode-markdown-extended

Extended syntaxes to built-in markdown & What you see is what you get exporter.
MIT License
125 stars 25 forks source link

Export to path outside of tree? #108

Open gimbo opened 3 years ago

gimbo commented 3 years ago

Maybe this isn't possible due to limitations of VSCode, but I was hoping to be able to do something like this:

  "markdownExtended.exportOutDirName": "~/Downloads",

in order to write exports to a folder outside of the current tree. Unfortunately that just creates & populates a folder called ~ at the top of the tree (so e.g. if I'm working on a tree of notes rooted at /tmp/foo it would create /tmp/foo/~/, etc. It's the same with absolute paths, e.g. setting exportOutDirName to /home/gimbo means the exported files are in /tmp/foo/home/gimbo/..., etc.

Is this insurmountable? I'd personally find it handy. :-)

qjebbs commented 3 years ago

~ is supported only in shell environment, you should use full path here.

gimbo commented 3 years ago

OK, thanks — but as I said:

It's the same with absolute paths, e.g. setting exportOutDirName to /home/gimbo means the exported files are in /tmp/foo/home/gimbo/..., etc.

I've just double-checked and it's still behaving that way: full path seems to make no difference, it still appears rooted in the notes tree.

Is that not the expected behaviour, then?

(In case there's a difference: this is while doing "Markdown: Export to File", i.e. exporting a single file; I haven't tried "Markdown: Export Markdown to File", which seems to do the whole tree — as in my case that produces 2GB of export 😀.)

serranomorante commented 1 year ago

I'm also having this issue. I need to export a PDF outside the source tree.