emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: JBash <bashveank@gmail.com>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Cc: emacs-orgmode Mode <emacs-orgmode@gnu.org>
Subject: Re: Basic beamer export
Date: Wed, 13 Mar 2013 00:52:49 -0400	[thread overview]
Message-ID: <CAJnMDSvBNAomN4nG9U1KMyCW-z0qtsEttu_o_fjOVBXWKu0-4g@mail.gmail.com> (raw)
In-Reply-To: <20130312144808.GC8127@kuru.dyndns-at-home.com>

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

Hi Suvayu,

I'm still having problems, but I'm getting slightly different results.
 With the same input file, the 3rd level headers are not exported as
subsubsections (rather than an enumerate).  I'm still not getting frames.
 I've attached the new output (from the same input file)  See inline

On Tue, Mar 12, 2013 at 10:48 AM, Suvayu Ali <fatkasuvayu+linux@gmail.com>wrote:

> Hi Jerry,
> On Tue, Mar 12, 2013 at 02:57:14AM -0400, JBash wrote:
> > Hello,
> >
> > I am apparently missing something very basic in the setup for beamer
> > export.  I have used
> http://orgmode.org/worg/exporters/beamer/ox-beamer.html as
> > a guide and have:
> [...]
> > in my .emacs file.  As you can see from the attached files, I'm getting
> > nested items rather than frames in the exported .tex file for the 3rd
> level
> > headlines, as I'd expect.  I am using Org-mode version 8.0-pre
> > (release_8.0-pre-33-g5c25ed and emacs 24.2.1.
> I cannot replicate this problem with your example.  I have a few
> questions though.
> 1. How do you check your org-version, M-x org-version RET?
Yes.  I just updated org.  I'm now at:
Org-mode version 8.0-pre (release_8.0-pre-54-gb5a853 @

> 2. Is the previously attached result with a minimal org setup?  If not,
>    you should try that.

 I stripped my .emacs file to a very simple setip.  I've attached it.

> 3. On first thought, you have a mixed installation and somehow the old
>    exporter is taking over.  I would suggest you go over the mixed
>    installation FAQ on Worg:
>    <http://orgmode.org/worg/org-faq.html#mixed-install>
Thanks for this link.  I had not found it before.  As mentioned above, my
M-x org-version looks "Good".

"M-x list-load-path-shadows" returns "Wrong type argument: stringp, nil"

Is that to be expected, or am I misunderstanding how to use that function?

> I suspect (3) because converting headlines to list is an old exporter
> behaviour.  A mixed install can happen if you do not update the
> load-path early enough in your setup before you start customising org
> variables.  I think the FAQ entry above is not complete since this
> information is missing, I'll try to update it when I can find the time.

Looks like you've already done it :).

> Hope this helps,
> --
> Suvayu
> Open source is the future. It sets us free.
> Thanks for your help.  Let me know if there are other things I can try.


[-- Attachment #1.2: Type: text/html, Size: 4120 bytes --]

[-- Attachment #2: dotemacs-stripped-jerry --]
[-- Type: application/octet-stream, Size: 2115 bytes --]

;;              Customization of Specific Packages                  ;;

;; ====== org-mode customizations ======================
;;(add-to-list 'load-path "~/emacs/lisp/org-mode/lisp")
(add-to-list 'load-path "/usr/share/emacs/site-lisp/org")
(add-to-list 'load-path "~/emacs/lisp/org-caldav/org-caldav-master")

;; === General Orgmode ===
(setq org-directory "/mnt/hgfs/jb4133/borg")
(setq org-todo-keywords
       '((sequence "TODO" "STARTED" "WAITING" "|" "DONE" "DELEGATED" "OBE")))

;; (require 'org-install) (deprecated since 7.9.3)
(add-to-list 'auto-mode-alist '("\\.org$" . org-mode))
(define-key global-map "\C-cl" 'org-store-link)
(define-key global-map "\C-ca" 'org-agenda)
(setq org-log-done t)
;; '(org-agenda-files (quote ("/mnt/hgfs/jb4133/borg/tasks.org"))))
(setq org-agenda-files (list "/mnt/hgfs/jb4133/borg/appointments.org"
(setq org-agenda-start-on-weekday nil)

;; Export to Beamer -  Presentation
(require 'ox-latex)
(add-to-list 'org-latex-classes
               ("\\section\{%s\}" . "\\section*\{%s\}")
               ("\\subsection\{%s\}" . "\\subsection*\{%s\}")
               ("\\subsubsection\{%s\}" . "\\subsubsection*\{%s\}")))

;; ====== "auto" configuration customizations ======================
 ;; custom-set-variables was added by Custom.
 ;; If you edit it by hand, you could mess it up, so be careful.
 ;; Your init file should contain only one such instance.
 ;; If there is more than one, they won't work right.
 ;; custom-set-faces was added by Custom.
 ;; If you edit it by hand, you could mess it up, so be careful.
 ;; Your init file should contain only one such instance.
 ;; If there is more than one, they won't work right.

[-- Attachment #3: beamer_attempt1-20130312.tex --]
[-- Type: application/x-tex, Size: 1671 bytes --]

  reply	other threads:[~2013-03-13  4:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12  6:57 Basic beamer export JBash
2013-03-12  9:34 ` Glyn Millington
2013-03-12 10:01   ` Glyn Millington
2013-03-12 10:21   ` JBash
2013-03-12 10:27     ` JBash
2013-03-12 14:48 ` Suvayu Ali
2013-03-13  4:52   ` JBash [this message]
2013-03-13 13:45     ` Suvayu Ali
2013-03-13 15:01       ` Achim Gratz
2013-03-15 14:59         ` JBash
2013-03-17 15:17           ` Suvayu Ali
2013-03-19 13:38             ` JBash
2013-03-17 13:08 ` Eric S Fraga
2013-03-17 15:02   ` 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:

  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=CAJnMDSvBNAomN4nG9U1KMyCW-z0qtsEttu_o_fjOVBXWKu0-4g@mail.gmail.com \
    --to=bashveank@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=fatkasuvayu+linux@gmail.com \


* 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


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).