emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Xin Shi <shixin111@gmail.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Org publish restrict to certain levels
Date: Thu, 23 Feb 2012 18:35:24 -0500	[thread overview]
Message-ID: <4502.1330040124@alphaville> (raw)
In-Reply-To: Message from Xin Shi <shixin111@gmail.com> of "Thu\, 23 Feb 2012 12\:46\:29 +0100." <CAJN7d84YdFzEGX4JQ7xxfsmcSbA63swP5sq8qPSfy_Hg61RQhw@mail.gmail.com>

Xin Shi <shixin111@gmail.com> wrote:

> I have a relatively long and detailed document maintained in org but
> only won't to publish into LaTeX to the first 3 levels, because the
> rest of the levels are too many details. If I use COMMENT into every
> of them, looks very cumbersome. I'm wondering if there is any in-file
> config to enable this. 

I thought it could be done through a combination of settings: an infile
setting of H:3 (or thereabouts) and a BIND setting of org-export-latex-low-levels to

C-h v org-export-latex-low-levels RET says:

| org-export-latex-low-levels is a variable defined in `org-latex.el'.
| Its value is itemize
| Documentation:
| How to convert sections below the current level of sectioning.
| This is specified by the `org-export-headline-levels' option or the
| value of "H:" in Org's #+OPTION line.
| This can be either nil (skip the sections), `description', `itemize',  <<<<< the doc says it can be nil to skip them
| or `enumerate' (convert the sections as the corresponding list type), or
| a string to be used instead of \section{%s}.  In this latter case,
| the %s stands here for the inserted headline and is mandatory.
| It may also be a list of three string to define a user-defined environment
| that should be used.  The first string should be the like
| "\begin{itemize}", the second should be like "\item %s %s" with up
| to two occurrences of %s for the title and a label, respectively.  The third
| string should be like "\end{itemize".
| You can customize this variable.

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


  reply	other threads:[~2012-02-23 23:35 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 [this message]
2012-03-27 21:09   ` Bastien
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:

  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=4502.1330040124@alphaville \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=shixin111@gmail.com \


* 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


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