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: Mon, 17 Dec 2018 20:54:18 +0100	[thread overview]
Message-ID: <87o99kc4k5.fsf@mat.ucm.es> (raw)
In-Reply-To: 87k1k8vxg2.fsf@alphaville.usersys.redhat.com


[-- Attachment #1.1: Type: text/plain, Size: 813 bytes --]


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

> You are probably loading ox-beamer which adds it and then loading the
> customized version which resets it. Try changing the order.

The setting in my .emacs is:
(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") 



So I changed that to
       (setq custom-file "/home/oub/emacs/init/custom-init.el")
        (load-file "/home/oub/emacs/init/custom-init.el") 
        (load-file "~/emacs/init/emacs_init.el")

Then the export works, but other problems occur. If I open a org file 

I receive a error message I attach, and indeed in that org file my
settings as defined in org_init are not all recognized.
Very strange indeed

Here is the error



[-- Attachment #1.2: org-bug.txt --]
[-- Type: text/plain, Size: 6196 bytes --]

Debugger entered--Lisp error: (void-function org--check-org-structure-template-alist)
  org--check-org-structure-template-alist(org-structure-template-alist)
  mapc(org--check-org-structure-template-alist (org-structure-template-alist org-tempo-keywords-alist))
  org-tempo-add-templates()
  org-tempo--update-maybe()
  org-tempo-setup()
  run-hooks(change-major-mode-after-body-hook text-mode-hook outline-mode-hook org-mode-hook)
  apply(run-hooks (change-major-mode-after-body-hook text-mode-hook outline-mode-hook org-mode-hook))
  run-mode-hooks(org-mode-hook)
  org-mode()
  set-auto-mode-0(org-mode nil)
  set-auto-mode()
  normal-mode(t)
  after-find-file(nil t)
  find-file-noselect-1(#<buffer beamer-exp.org> "~/ALLES/HGs/tex/vorlesungen/HGMetNum/Practicas/Prac5/Org-files/beamer-exp.org" nil nil "~/ALLES/HGs/tex/vorlesungen/HGMetNum/Practicas/Prac5/Org-files/beamer-exp.org" (9324866 2050))
  find-file-noselect("/home/oub/ALLES/HGs/tex/vorlesungen/HGMetNum/Practicas/Prac5/Org-files/beamer-exp.org" nil nil nil)
  #f(compiled-function (filename &optional wildcards) "Edit file FILENAME.\nSwitch to a buffer visiting file FILENAME,\ncreating one if none already exists.\nInteractively, the default if you just type RET is the current directory,\nbut the visited file name is available through the minibuffer history:\ntype \\[next-history-element] to pull it into the minibuffer.\n\nThe first time \\[next-history-element] is used after Emacs prompts for\nthe file name, the result is affected by `file-name-at-point-functions',\nwhich by default try to guess the file name by looking at point in the\ncurrent buffer.  Customize the value of `file-name-at-point-functions'\nor set it to nil, if you want only the visited file name and the\ncurrent directory to be available on first \\[next-history-element]\nrequest.\n\nYou can visit files on remote machines by specifying something\nlike /ssh:SOME_REMOTE_MACHINE:FILE for the file name.  You can\nalso visit local files as a different user by specifying\n/sudo::FILE for the file name.\nSee the Info node `(tramp)File name Syntax' in the Tramp Info\nmanual, for more about this.\n\nInteractively, or if WILDCARDS is non-nil in a call from Lisp,\nexpand wildcards (if any) and visit multiple files.  You can\nsuppress wildcard expansion by setting `find-file-wildcards' to nil.\n\nTo visit a file without any kind of conversion and without\nautomatically choosing a major mode, use \\[find-file-literally]." (interactive #f(compiled-function () #<bytecode 0x342cc75>)) #<bytecode 0x232d53>)("/home/oub/ALLES/HGs/tex/vorlesungen/HGMetNum/Practicas/Prac5/Org-files/beamer-exp.org" nil)
  ad-Advice-find-file(#f(compiled-function (filename &optional wildcards) "Edit file FILENAME.\nSwitch to a buffer visiting file FILENAME,\ncreating one if none already exists.\nInteractively, the default if you just type RET is the current directory,\nbut the visited file name is available through the minibuffer history:\ntype \\[next-history-element] to pull it into the minibuffer.\n\nThe first time \\[next-history-element] is used after Emacs prompts for\nthe file name, the result is affected by `file-name-at-point-functions',\nwhich by default try to guess the file name by looking at point in the\ncurrent buffer.  Customize the value of `file-name-at-point-functions'\nor set it to nil, if you want only the visited file name and the\ncurrent directory to be available on first \\[next-history-element]\nrequest.\n\nYou can visit files on remote machines by specifying something\nlike /ssh:SOME_REMOTE_MACHINE:FILE for the file name.  You can\nalso visit local files as a different user by specifying\n/sudo::FILE for the file name.\nSee the Info node `(tramp)File name Syntax' in the Tramp Info\nmanual, for more about this.\n\nInteractively, or if WILDCARDS is non-nil in a call from Lisp,\nexpand wildcards (if any) and visit multiple files.  You can\nsuppress wildcard expansion by setting `find-file-wildcards' to nil.\n\nTo visit a file without any kind of conversion and without\nautomatically choosing a major mode, use \\[find-file-literally]." (interactive #f(compiled-function () #<bytecode 0x342cdb5>)) #<bytecode 0x232d53>) "/home/oub/ALLES/HGs/tex/vorlesungen/HGMetNum/Practicas/Prac5/Org-files/beamer-exp.org")
  apply(ad-Advice-find-file #f(compiled-function (filename &optional wildcards) "Edit file FILENAME.\nSwitch to a buffer visiting file FILENAME,\ncreating one if none already exists.\nInteractively, the default if you just type RET is the current directory,\nbut the visited file name is available through the minibuffer history:\ntype \\[next-history-element] to pull it into the minibuffer.\n\nThe first time \\[next-history-element] is used after Emacs prompts for\nthe file name, the result is affected by `file-name-at-point-functions',\nwhich by default try to guess the file name by looking at point in the\ncurrent buffer.  Customize the value of `file-name-at-point-functions'\nor set it to nil, if you want only the visited file name and the\ncurrent directory to be available on first \\[next-history-element]\nrequest.\n\nYou can visit files on remote machines by specifying something\nlike /ssh:SOME_REMOTE_MACHINE:FILE for the file name.  You can\nalso visit local files as a different user by specifying\n/sudo::FILE for the file name.\nSee the Info node `(tramp)File name Syntax' in the Tramp Info\nmanual, for more about this.\n\nInteractively, or if WILDCARDS is non-nil in a call from Lisp,\nexpand wildcards (if any) and visit multiple files.  You can\nsuppress wildcard expansion by setting `find-file-wildcards' to nil.\n\nTo visit a file without any kind of conversion and without\nautomatically choosing a major mode, use \\[find-file-literally]." (interactive #f(compiled-function () #<bytecode 0x3190505>)) #<bytecode 0x232d53>) "/home/oub/ALLES/HGs/tex/vorlesungen/HGMetNum/Practicas/Prac5/Org-files/beamer-exp.org")
  find-file("/home/oub/ALLES/HGs/tex/vorlesungen/HGMetNum/Practicas/Prac5/Org-files/beamer-exp.org")
  dired-find-file()
  funcall-interactively(dired-find-file)
  call-interactively(dired-find-file nil nil)
  command-execute(dired-find-file)

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

  reply	other threads:[~2018-12-17 19:54 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 [this message]
2018-12-18  3:22     ` Nick Dokos
2018-12-18  8:13       ` Uwe Brauer

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=87o99kc4k5.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).