emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: "Colin Fraizer" <orgmode@cfraizer.com>
To: emacs-orgmode@gnu.org
Subject: Bug in inlinetask export or latex export?
Date: Wed, 20 Apr 2011 08:28:32 -0400	[thread overview]
Message-ID: <007801cbff56$77046c40$650d44c0$@cfraizer.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1544 bytes --]

I have a document that looks like the following.

 

If I export the whole file, I get the whole file. (I'm exporting to LaTeX
using C-c C-e d.)

 

If I move to the line "** Level 2 A" and export that subtree using C-c C-e 1
d, the inline tasks are omitted.

 

Is this a bug or have I just misconfigured this somehow?

 

It seems to be caused by the fact that those inline tasks are treated as
"lines before the first headline" and that org-export-latex-first-lines
calls org-export-preprocess-string with a more-or-less hardcoded opt-plist
that doesn't include :tasks.

 

Is there a reason not to modify this section of
org-export-latex-first-lines:

         (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)                    ;; <--
this is the line I want to add

           :timestamps (plist-get opt-plist :timestamps)

           :footnotes (plist-get opt-plist :footnotes)))

 

----------------------------------------------------------------------

* Level 1 A

** Level 2 A

test

*************** TODO Test 1

*************** END

*************** TODO Test 2

*************** END

*************** TODO Test 3

*************** END

test2

and more

 

** Level 2 B

----------------------------------------------------------------------


[-- Attachment #2: Type: text/html, Size: 7526 bytes --]

                 reply	other threads:[~2011-04-20 12:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='007801cbff56$77046c40$650d44c0$@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

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).