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

From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [Bug] beamer backend and org-reload
Date: Tue, 5 Mar 2013 21:26:07 +0100	[thread overview]
Message-ID: <20130305202607.GO7544@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <87obex1z4h.fsf@Rainer.invalid>

Hi Achim,

On Tue, Mar 05, 2013 at 07:26:54PM +0100, Achim Gratz wrote:
> Suvayu Ali writes:
> > That said, I have noticed something odd about the new exporter and
> > org-reload.  I think with the new exporter after doing org-reload, org
> > related config is not reloaded properly.
> 
> Config is not reloaded at all (and never has been), any configuration
> variables that are already existing are not touched when the file gets
> reloaded.
> 
> > This borks the Org instance.  This is more visible when using the
> > Beamer backend since it requires customisation of org-latex-classes by
> > the user.  One of these days, I'll try to come up with a proper recipe
> > to reproduce this.
> 
> Please do, this should not happen.

Here is the recipe:

1. emacs -nw -Q -l ~/minimal-org.el

   ;;; minimal-org.el: Minimal setup to load latest `org-mode'
   
   ;;; Code:
   (setq debug-on-error t
         debug-on-signal nil
         debug-on-quit nil)
   
   (add-to-list 'load-path (expand-file-name "~/build/org-mode/lisp"))
   
   (require 'ox-beamer)
   (add-to-list 'org-latex-classes
                '("beamer"
                  "\\documentclass\[presentation\]\{beamer\}"
                  ("\\section\{%s\}" . "\\section*\{%s\}")
                  ("\\subsection\{%s\}" . "\\subsection*\{%s\}")
                  ("\\subsubsection\{%s\}" . "\\subsubsection*\{%s\}")))

2. C-x C-f some-file.org RET
3. Now try to export: C-c C-e.  You can see menu options for beamer export.
4. Now reload Org: C-c C-x !.  Try step 3 again.  You will notice the
   entries for beamer is missing.

This might actually be a problem with ox-beamer and not org-reload
because I noticed my other Org customisations do stay intact (which is
of course in line with your comment about settings not being touched).

Instead of step (3), you could also try M-x org-beamer-export-as-latex.
After step (4), repeating this alternate step (3) should give you the
following backtrace.

Debugger entered--Lisp error: (error "Unknown \"beamer\" back-end: Aborting export")
  signal(error ("Unknown \"beamer\" back-end: Aborting export"))
  error("Unknown \"%s\" back-end: Aborting export" beamer)
  org-export-barf-if-invalid-backend(beamer)
  org-export-as(beamer nil nil nil nil)
  org-export-to-buffer(beamer "*Org BEAMER Export*" nil nil nil nil)
  org-beamer-export-as-latex()
  call-interactively(org-beamer-export-as-latex record nil)
  command-execute(org-beamer-export-as-latex record)
  execute-extended-command(nil "org-beamer-export-as-latex")
  call-interactively(execute-extended-command nil nil)
  command-execute(execute-extended-command)

Hopefully my recipe is complete to fix this issue.

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

next prev parent reply	other threads:[~2013-03-05 20:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-05 15:18 URGENT Need help fixing beamer exporting, can someone jump on IRC? James Harkins
2013-03-05 15:28 ` James Harkins
2013-03-05 15:42   ` Achim Gratz
2013-03-05 15:44   ` Suvayu Ali
2013-03-05 18:26     ` Achim Gratz
2013-03-05 20:26       ` Suvayu Ali [this message]
2013-03-05 20:50         ` [Bug] beamer backend and org-reload Achim Gratz
2013-03-05 22:26           ` Suvayu Ali
2013-03-05 23:29         ` Nicolas Goaziou
2013-03-06 12:10           ` Suvayu Ali

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=20130305202607.GO7544@kuru.dyndns-at-home.com \
    --to=fatkasuvayu+linux@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).