From: Manish <email@example.com>
To: David St-Hilaire <firstname.lastname@example.org>
Subject: Re: elisp code location?
Date: Mon, 19 Jan 2009 23:50:12 +0530 [thread overview]
Message-ID: <email@example.com> (raw)
On Mon, Jan 19, 2009 at 11:33 PM, David St-Hilaire wrote:
> Manish wrote:
>> Some of the publishing options can be kept in the org file itself but
>> some others would need to defined as part of org-publish-project-alist
>> itself only. Is there a reason why you do not wish to keep the settings
>> in .emacs file?
> No reason, I was just trying to understand how to publishing system
> works. I couldn't make it work so far. I now have setup my project
> alist in my .emacs file (and reloaded my .emacs) and when I try to
> publish my project, nothing happens...
> Here is what I added to my .emacs:
> (setq org-publish-project-alist
> :base-directory "/home/dave/projet/maitrise/memoire"
> :publishing-directory "/home/dave/projet/maitrise/memoire/html"
> :section-numbers nil
> :table-of-contents t
> :publishing-function org-publish-org-to-html)))
> A strange thing I noticed is that when I use M-x and type org-publish
> then press tab, I only get:
> Possible completions are:
> org-publish org-publish-all
> org-publish-current-file org-publish-current-project
org-publish-org-to-html is not an interactive function hence not
available with M-x. You only need to execute org-publish (or C-c C-e X)
and publish "plan".
> and thus org-publish-org-to-html doesn't seem to be there... I
> installed org-mode throuhg gentoo emerge and am at the version 6.05b,
> is this version too old to use publishing?
Can't say.. but new features/fixes keep happening in Org at such a pace
that it's worth staying as close to the cutting edge as possible. As
Scot mentioned it's super easy to upgrade either using the shell-script
or by just using the git version itself (see FAQ for details.)
next prev parent reply other threads:[~2009-01-19 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 16:13 elisp code location? David St-Hilaire
2009-01-19 16:49 ` Manish
2009-01-19 18:03 ` David St-Hilaire
2009-01-19 18:08 ` Scot Becker
2009-01-19 18:20 ` Manish [this message]
2009-01-19 18:22 ` Matthew Lundin
2009-01-19 19:02 ` David St-Hilaire
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 \
* 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).