From: "Colin Fraizer" <orgmode@cfraizer.com>
To: emacs-orgmode@gnu.org
Subject: Bug Report: latex export interaction with inlinetasks
Date: Sat, 8 Oct 2011 04:17:56 -0400 [thread overview]
Message-ID: <002901cc8592$cadd6c50$609844f0$@cfraizer.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1800 bytes --]
I have a file like this:
* Item 1
- list1a
- list1b
* Item 2
- list2a
*************** TODO Test
*************** END
- list2b
* Item 3
(1) If I export the whole file to LaTeX, everything works fine.
(2) If I export the subtree "* Item 2" to HTML, everything works fine.
(I see my list and the inlinetask in that list.)
(3) If I export the subtree "* Item 2" to LaTeX, the inlinetask is
removed. (All inlinetasks are removed from list2.)
NOTE: I'm exporting the subtrees with C-c C-e 1 d (or C-c C-e 1 L).
This is apparently caused by the fact that:
1. org-export-latex-first-lines matches all of list2 (because there
are no headlines under "* Item 2"); AND
2. org-export-preprocess-string is called with limited parameters on
those first lines. Those parameters do not include my value for ":tasks".
Is there a reason why we could not (or should not) change the defun
org-export-latex-first-lines like the following. I only add the line
":tasks (plist-get opt-plist :tasks)"
I'm not familiar enough with the guts of org to know if that will have
terrible consequences elsewhere.
(defun org-export-latex-first-lines (opt-plist &optional beg end)
:
:
(prog1
(org-export-latex-content
(org-export-preprocess-string
(buffer-substring pt end)
:for-backend 'latex
:emph-multiline t
:add-text nil
:comments nil
:skip-before-1st-heading nil
:LaTeX-fragments nil
:tasks (plist-get opt-plist :tasks) ;; *** I PROPOSE ADDING THIS
LINE
:timestamps (plist-get opt-plist :timestamps)
:footnotes (plist-get opt-plist :footnotes)))
:
:
) ; end of defun
[-- Attachment #2: Type: text/html, Size: 13747 bytes --]
next reply other threads:[~2011-10-08 8:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-08 8:17 Colin Fraizer [this message]
2011-10-09 12:05 ` Bug Report: latex export interaction with inlinetasks Nicolas Goaziou
2011-10-09 12:58 ` Colin Fraizer
2011-10-13 11:49 ` Nicolas Goaziou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002901cc8592$cadd6c50$609844f0$@cfraizer.com' \
--to=orgmode@cfraizer.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).