#DIGIME TO EXPORT COMMENTS HOW TO#

Note that you may need to remove the byte-compiled org-latex.elc file in order to see your changes in org-latex.el propagate through to the export. Maybe something in the thread Jonathan set up will shed some light on this subject. This isn't the most convenient way of doing things, and I'm not sure of a way to specify the :comments parameter on a per-file basis. Would be exported as this is text before a comment So in your case this is text before a comment Private Sub ApplicationNewMailEx(ByVal EntryIDCollection As String) Dim outlookApp As Outlook.Application Dim objectNS As Outlook.NameSpace Dim inboxItems As. If, in the org-export-as-latex function, you replace :comments nil with :comments '%% %s', then this will insert a '%' in front of whatever the comment text is upon export. When an e-mail is added to this folder the following code is executed, where the Title, Date and Body text is passed to another macro which open an Excel file and to paste the data.

#DIGIME TO EXPORT COMMENTS HOW TO#

Essentially, the :comments parameter can be a format string showing how to handle the comments if it is nil, this means no format handling so nothing is printed. This parameter tells the org-mode exporter what to do with comments - for the details look at the call to and implementation of org-export-handle-comments in org-exp.el. One of the things passed to the org-export-preprocess-string function is a parameter list, in particular it contains a :comments parameter, which in the LaTeX case is set to nil. If you look in the org-export-as-latex function in org-latex.el, you can find calls to org-export-preprocess-string. Each exporter backend is different, but let us consider the LaTeX backend. Comments are handled in the org-export-handle-comments function, which is called by org-export-preprocess-string in org-exp.el. In addition to Jonathan Leech-Pepin's answer, there is a hackish way of doing it for a given exporter backend.

Digime to export comments