emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: cannot export to beamer, even with (require 'ox-beamer) [9.1.14 (release_9.1.14-1059-gadec50 @ /home/oub/emacs/site-lisp/packages/org/)]
Date: Tue, 18 Dec 2018 09:13:14 +0100	[thread overview]
Message-ID: <874lbb5k2t.fsf@mat.ucm.es> (raw)
In-Reply-To: 874lbbwmbf.fsf@alphaville.usersys.redhat.com

[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]


   > Uwe Brauer <oub@mat.ucm.es> writes:

   > If your only problem with the original order was what you described before,
   > don't change the order: just do

   > (load-file "~/emacs/init/emacs_init.el")
   > (setq custom-file "/home/oub/emacs/init/custom-init.el")
   > (load-file "/home/oub/emacs/init/custom-init.el")
   > (require 'ox-beamer)

   > and delete the original `(require 'ox-beamer)' from wherever it was
   > before (presumably in ~/emacs/init/emacs_init.el). You are only trying
   > to avoid the loading of your customizations from clobbering
   > org-latex-classes.

   > BTW, the fact that you *do* have problems when you change the order,
   > probably means that there is strong coupling between your init files
   > which is not a good thing. You might want to spend some time
   > refactoring them and breaking interdependencies. If you decide to do
   > that, small steps (and good backups) are probably a good idea.

Right, that is the feeling I am starting to share. I might do that. thanks

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 4393 bytes --]

      reply	other threads:[~2018-12-18  8:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-17  8:07 Bug: cannot export to beamer, even with (require 'ox-beamer) [9.1.14 (release_9.1.14-1059-gadec50 @ /home/oub/emacs/site-lisp/packages/org/)] Uwe Brauer
2018-12-17 18:07 ` Nick Dokos
2018-12-17 19:54   ` Uwe Brauer
2018-12-18  3:22     ` Nick Dokos
2018-12-18  8:13       ` Uwe Brauer [this message]

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=874lbb5k2t.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --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
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).