emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode <emacs-orgmode@gnu.org>, Xin Shi <shixin111@gmail.com>
Subject: Re: Org publish restrict to certain levels
Date: Tue, 27 Mar 2012 23:09:28 +0200	[thread overview]
Message-ID: <87pqbxpx87.fsf@gnu.org> (raw)
In-Reply-To: <4502.1330040124@alphaville> (Nick Dokos's message of "Thu, 23 Feb 2012 18:35:24 -0500")

Hi Nick,

Nick Dokos <nicholas.dokos@hp.com> writes:

> Unfortunately, there is a bug in org-latex.el, in org-export-latex-subcontent
>
> ,----
> | 	    ((listp org-export-latex-low-levels)
> | 	     (if (string-match "% ends low level$"
> | 			       (buffer-substring (point-at-bol 0) (point)))
> | 		 (delete-region (point-at-bol 0) (point))
> | 	       (insert (car org-export-latex-low-levels) "\n"))     ;;;; <<<< org-export-latex-low-levels cannot be nil here: car will blow up
> | 	     (insert (format (nth 2 org-export-latex-low-levels)    ;;;; <<<< or here: format will blow up
> | 			     heading
> | 			     (if label (format "\\label{%s}" label) "")))
> | 	     (insert (org-export-latex-content content))
> | 	     (cond ((stringp subcontent) (insert subcontent))
> | 		   ((listp subcontent) (org-export-latex-sub subcontent)))
> | 	     (insert (nth 1 org-export-latex-low-levels)
> | 		     " %% ends low level\n"))
> | 
> `----

This is fixed -- you can now set `org-export-latex-low-levels' to nil,
low levels won't be exported.

Thanks,

-- 
 Bastien

  reply	other threads:[~2012-03-27 23:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23 11:46 Org publish restrict to certain levels Xin Shi
2012-02-23 23:35 ` Nick Dokos
2012-03-27 21:09   ` Bastien [this message]
2012-03-28  1:20     ` Nick Dokos
2012-03-28  7:53       ` Xin Shi

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=87pqbxpx87.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.com \
    --cc=shixin111@gmail.com \
    /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).