emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: list-load-path-shadows
Date: Wed, 05 Sep 2012 14:00:54 -0400	[thread overview]
Message-ID: <6932.1346868054@alphaville.americas.hpqcorp.net> (raw)
In-Reply-To: Message from tsd@tsdye.com (Thomas S. Dye) of "Wed, 05 Sep 2012 06:57:48 -1000." <m1ipbso19v.fsf@tsdye.com>

Thomas S. Dye <tsd@tsdye.com> wrote:

> The initialization error was coming when one of my files was being
> evaluated.  If I don't require org-latex, the compiled version of org
> will initialize.
> 
> *** OFF Require org-latex
> #+begin_src emacs-lisp :tangle no
>   (require 'org-latex)
> #+end_src
> 

That's not what the previous backtrace showed though: the ditaa path
calculation was directly implicated.

In any case, the above shouldn't happen as long as you have done
``make autoloads'' or equivalent and 

   (require 'org-install)

beforehand, and in fact it does not happen in my case:

  emacs -q -l /path/to/minimal/.emacs

with the following minimal .emacs, starts up without error:

--8<---------------cut here---------------start------------->8---
;;; -*- mode: emacs-lisp -*-
;;; constant part
(add-to-list 'load-path (expand-file-name "~/src/emacs/org/org-mode/lisp"))
(add-to-list 'load-path (expand-file-name "~/src/emacs/org/org-mode/contrib/lisp"))

(add-to-list 'auto-mode-alist '("\\.\\(org\\|org_archive\\|txt\\)$" . org-mode))

(require 'org-install)

(setq debug-on-error t)
(setq debug-on-quit t)
(setq eval-expression-print-length nil)
(setq eval-expression-print-level nil)

(global-set-key "\C-cl" 'org-store-link)
(global-set-key "\C-ca" 'org-agenda)

(require 'org-latex)
--8<---------------cut here---------------end--------------->8---


OTOH, even if I leave out the (require 'org-install), I get no error
(and that's after removing the org that came with emacs and making sure
that I have compiled everything), so I'm a bit baffled right now.

Nick

  reply	other threads:[~2012-09-05 18:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-04 16:33 list-load-path-shadows Thomas S. Dye
2012-09-04 17:34 ` list-load-path-shadows Nick Dokos
2012-09-05  3:16   ` list-load-path-shadows Thomas S. Dye
2012-09-05 13:54     ` list-load-path-shadows Nick Dokos
2012-09-05 16:57       ` list-load-path-shadows Thomas S. Dye
2012-09-05 18:00         ` Nick Dokos [this message]
2012-09-05 18:51           ` list-load-path-shadows Thomas S. Dye
2012-09-05 19:20             ` list-load-path-shadows Nick Dokos
2012-09-05 19:40               ` list-load-path-shadows Thomas S. Dye
2012-09-05 20:01                 ` list-load-path-shadows Nick Dokos
2012-09-05 20:58                   ` list-load-path-shadows Thomas S. Dye

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=6932.1346868054@alphaville.americas.hpqcorp.net \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tsd@tsdye.com \
    /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).