From: "François Pinard" <pinard@iro.umontreal.ca>
To: emacs-orgmode@gnu.org
Subject: Installation problem? (new exporter)
Date: Mon, 11 Feb 2013 16:46:46 -0500 [thread overview]
Message-ID: <86d2w6ikvt.fsf@iro.umontreal.ca> (raw)
Hi, gang.
I've difficulty to get the new exporter into movement. After trying for
some time, I'm giving into this mailing list for help or advice.
First, "C-c C-e" yields "Cannot open load file: org-export". I guess
that some old autoload is hiding somewhere, but I just do not find it.
Command "C-h k C-c C-e" tersely says:
org-export-dispatch is an interactive autoloaded Lisp function.
[Arg list not available until function definition is loaded.]
Not documented.
Debugging on error is terse as well:
Debugger entered--Lisp error: (file-error "Cannot open load file" "org-export")
On this Ubuntu 12.10, I moved /usr/share/emacs/23.4/lisp/org/ and
/share/emacs23/site-lisp/org-mode/ elsewhere, just in case. I had no
problems before using a recent Org, letting these older directories
there, but this does not mean there were no problem, of course.
To install Org, I merely "git clone" or "git pull" it, and then use
"make". In the Make output, I see that autoloads are regenerated.
Second, the following Makefile entry (reduced) does not work anymore for
me:
all:
emacs -Q --batch --load publish.el --funcall org-publish-all
Here is file "publish.el" (reduced):
(defvar api-org-distribution "~/emacs/_/org-mode")
(add-to-list 'load-path (concat api-org-distribution "/lisp"))
(require 'org)
(message (org-version))
(setq org-publish-project-alist
`(("api"
:base-directory "~/control3/api/"
:publishing-directory "~/control3/api-html"
)))
The "~/control3/api/" directory is already populated with many Org files
by another program. Running "make" yields:
7.9.3e
No publishing function chosen
and no output is produced. Sigh! :-)
François
reply other threads:[~2013-02-11 21:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=86d2w6ikvt.fsf@iro.umontreal.ca \
--to=pinard@iro.umontreal.ca \
--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).