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

From: Rafael <rvf0068@gmail.com>
To: Emacs-orgmode list <emacs-orgmode@gnu.org>
Subject: Bug in org-beamer-publish-to-pdf?
Date: Sun, 23 Mar 2014 22:22:05 -0600	[thread overview]
Message-ID: <86k3bkxm36.fsf@gmail.com> (raw)


Hi all,

Using Org-mode version 8.2.5h (release_8.2.5h-829-g9665f8) from git, and
GNU Emacs 24.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.4.2) of 2014-02-22
on king, modified by Debian

I think there is a bug in org-beamer-publish-to-pdf. The code of the
function is:

#+BEGIN_SRC emacs-lisp
  (defun org-beamer-publish-to-pdf (plist filename pub-dir)
    (org-publish-attachment
     plist
     (org-latex-compile (org-publish-org-to 'beamer filename ".tex" plist))
     pub-dir))
#+END_SRC

It seems to me that (org-publish-org-to 'beamer filename ".tex" plist)
only returns filename.tex without the directory. Hence org-latex-compile
wants to compile a .tex file in my home directory, (rather than at the base
directory of the publishing) and fails at not finding it there. 

Certainly not the most elegant solution, but the following works for
me. Although only with (setq org-latex-pdf-process '("texi2dvi -p -b -V %f")),
since with the default setting for org-latex-pdf-process, still pdflatex
complains about not being able to write to the log file.

#+BEGIN_SRC emacs-lisp
  (defun org-beamer-publish-to-pdf (plist filename pub-dir)
    (org-publish-attachment
     plist
     (org-latex-compile (concat
                         (plist-get plist :base-directory)
                         (substring (org-publish-org-to 'beamer filename ".tex" plist) 1 nil)
                         ))
     pub-dir))
#+END_SRC

next             reply	other threads:[~2014-03-24  4:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24  4:22 Rafael [this message]
2014-03-24 13:00 ` Bug in org-beamer-publish-to-pdf? 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=86k3bkxm36.fsf@gmail.com \
    --to=rvf0068@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).