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

From: James Harkins <jamshark70@gmail.com>
To: orgmode <emacs-orgmode@gnu.org>
Subject: Temp files are not deleted after beamer export with source code blocks
Date: Tue, 29 Oct 2013 11:00:57 +0800	[thread overview]
Message-ID: <efafe53a-cfe0-4add-91ac-cd1017a8aa54@dewdrop-world.net> (raw)

I've set org-latex-listings to "Use listings" (not minted), and then run 
this minimal example.

~~~~
#+BIND: org-latex-listings-options (("basicstyle" "\\ttfamily") 
("captionpos" "b") ("tabsize" "3"))

#+LANGUAGE:  en
#+OPTIONS:   H:1 num:t toc:nil \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t ':t
#+EXPORT_SELECT_TAGS: export
#+EXPORT_EXCLUDE_TAGS: noexport

#+startup: beamer
#+LaTeX_CLASS: beamer
#+LaTeX_CLASS_OPTIONS: [presentation]
#+BEAMER_THEME: default
#+COLUMNS: %45ITEM %10BEAMER_env(Env) %10BEAMER_act(Act) %4BEAMER_col(Col) 
%8BEAMER_opt(Opt)
#+PROPERTY: BEAMER_col_ALL 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 0.0 :ETC

#+LATEX_HEADER: \usepackage{listings}

#+TITLE:     Test
#+AUTHOR:    hjh

* A frame
** You can write some code like this.
#+begin_src {} -i :exports code
some code here
#+end_src
~~~~

Now there is a file "beamer-listings-2.vrb" containing the LaTeX code for 
the second frame. This file never gets deleted. As I'm developing the 
presentation, chances are that frame will end up becoming a different frame 
number, so I keep getting more and more vrb files on disk.

Shouldn't org clean these up after LaTeX is finished? It already cleans up 
other temporary LaTeX files.

hjh

next             reply	other threads:[~2013-10-29  3:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-29  3:00 James Harkins [this message]
2013-10-29  8:06 ` Temp files are not deleted after beamer export with source code blocks Nicolas Goaziou
2013-10-29  9:16   ` James Harkins
2013-10-29 13:19     ` Nicolas Goaziou
2013-11-06  9:44   ` James Harkins
2013-11-06 14:15     ` Nicolas Goaziou
2013-11-07  1:34       ` James Harkins
2013-11-07 16:21         ` Nicolas Goaziou
2013-11-08  7:14           ` James Harkins
2013-11-08  7:59             ` 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=efafe53a-cfe0-4add-91ac-cd1017a8aa54@dewdrop-world.net \
    --to=jamshark70@gmail.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).