Home → Problems (v2) →

Latex Export - Snippet Generation fails

• Edit

Alex

17 Jun, 2013 11:50 AM

I have a problem with the snippet generation for tex export. I installed the newest version 2.3.2 (15)(not sandboxed) and I can't generate tex snippets. Not if I use no meta data, not if I only specify baseheaderlevel. I inferred from the documentation on the memory leak that composer should run on mmd 4 so this is a feature that should be available? Any help to get this working would be appreciated.

1. 1 Posted by Alex on 17 Jun, 2013 01:19 PM

   

   On another note, it might be useful to be able to disable full document generation via a specific metadata tag as well. I know this would require a change to markdown itself, which isn't the scope of this forum but using composer I run into the problem of wanting to link a bibtex file to my document (so that it shows up in the reference hud) while still needing the snippet functionality. However, this is independent of my former bug report.

   • Edit

2. Support Staff 2 Posted by Fletcher on 17 Jun, 2013 07:13 PM

   

   Alex,

   Thanks for writing, and sorry you're having trouble.

   What do you mean you can't export snippets? What exactly are you doing, what happens, and what do you expect to happen? It works fine for me when I export as LaTeX.

   Fletcher

   • smime.p7s 4.78 KB
   • Edit

3. Support Staff 3 Posted by Fletcher on 17 Jun, 2013 07:18 PM

   

   Just select what you want to convert, and use the "Copy As..." feature. You can convert selected portions of your document, including everything except metadata.

   F-

   • smime.p7s 4.78 KB
   • Edit

4. 4 Posted by Alex on 17 Jun, 2013 07:53 PM

   

   Hey Fletcher,

   thanks for the fast response! If I create a new Markdown file without metadata, put some text into it (ex. just a headline and a paragraph) and export it to tex, the resulting file has \end{document} appended. As I understand it this means that full document mode was triggered.

   What I would expect is a tex snippet without \end{document}, so that I can feed it into my tex master file.

   I have also noticed that the copy as feature works as expected when no metadata is selected.

   I have checked this behavior with composer versions 2.3.2 as well as the one before which I think was 2.2?

   And to your second response, yeah I could do that, however I wanted to automate the pdf generation as much as possible (so selecting and copy as would be not an optimal solution).

   Aside from all of this, I will probably have to go the advanced route with the custom export script to get it to work just right.

   • Edit

5. Support Staff 5 Posted by Fletcher on 17 Jun, 2013 08:04 PM

   

   It works fine exporting without \end{document}, as long as there is truly no metadata attached.

   Did you add the MathJax metadata to your document automatically in the preferences? That would trigger a complete document when exporting.

   F-

   • smime.p7s 4.78 KB
   • Edit

6. 6 Posted by Alexander Herwi... on 17 Jun, 2013 08:14 PM

   

   Hey Fletcher,

   alright, I kind of feel embarrassed now. That was it... -.-

   Thank you for your quick help! Keep up the great work!

   Cheers, Alex

   Am 17.06.2013 um 22:04 schrieb "Fletcher" <[email blocked]>:

   • Edit

7. Support Staff 7 Posted by Fletcher on 17 Jun, 2013 09:11 PM

   

   No worries. I'm updating MMD so it will ignore this sort of metadata (`html header`) when exporting latex.

   F-

   • smime.p7s 4.78 KB
   • Edit