emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Puneeth <punchagan@gmail.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Org-jekyll - org-publish-initialize-files-alist
Date: Tue, 29 Jun 2010 23:49:04 -0400	[thread overview]
Message-ID: <11902.1277869744@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Puneeth <punchagan@gmail.com> of "Wed, 30 Jun 2010 08:57:33 +0530." <AANLkTilRbuEm8tju9q5vscFKVGIR6bDPJ96yGAlmfDHr@mail.gmail.com>

Puneeth <punchagan@gmail.com> wrote:

> Hi,
> 
> On Wed, Jun 30, 2010 at 4:15 AM, Nathan Neff <nathan.neff@gmail.com> wrote:
> [..]
> > I tried putting this in my emacs, but it didn't work:
> > (require 'org-protocol.el)
> > (require 'org-publish)
> > (require 'org-jekyll)
> 
> I haven't used Jekyll, but should it be just org-protocol and not
> org-protocol.el?
> (require 'org-protocol)
> 

That's true: the first argument of `require' should be the symbol that
is `provide'-ed by the load file. E.g. org-protocol.el ends with

,----
| ...
| (provide 'org-protocol)
`----

so the `require' form should indeed be 

 (require 'org-protocol)

- and there is an additional convention that the filename should then be
the printname of the `provide'-ed symbol, with ".el" appended:
org-protocol.el in this case (but the convention can be overridden - see
the documentation of `require' for details).

The function that Nathan was asking about was originally defined in
org-publish.el which does

,----
| ...
| 
| (provide 'org-publish)
`----

so normally, doing

   (require 'org-publish)

would be enough to load the file and therefore define the function.
However, nothing is going to help in this case, because the function,
even though it is declared and used in org-protocol.el, was deleted from
org-publish.el with this commit:

,----
| commit 339d6fe4bbf7b9858c6323d01f32d0c73a4cd3a8
| Author: Sebastian Rose <sebastian_rose@gmx.de>
| Date:   Thu May 13 13:43:53 2010 +0200
| 
|     Publishing, cashing and timestamps
|     
|     Carsten Dominik <carsten.dominik@gmail.com> writes:
|     > Hi Sebastian,
|     >
|     > sorry for being slow.  Could you do me a favor and send me the cache patch one
|     > more time - if possible updated to the current master.
|     >
|     > I am just not sure I have the right patch in my hands.
|     
|     Hi Carsten,
|     
|     no problem. The patch is attached.
|     
|     Here is a list of my ChangeLog entries, redated to today:
|     
|     2010-05-13  Sebastian Rose  <sebastian_rose@gmx.de>
|     
|     	* org-publish.el (org-publish-cache): Use one big hashmap for
|     	each project defined in `org-publish-project-alist'. The
|     	hashmap will hold pairs of our timestamp-filenames and
|     	timestamps, as well as pairs of source-paths and associated
|     	plists for arbitrary values. Currently only the files title is
|     	stored there.
|     
|     	The caching feature writes the information gathered during
|     	publishing to disk and re-loads it from there the next time we
|     	publish the same project.  All those informations will hence
|     	survive a restart of emacs.
|     
|     	One cache file per publishing project is used. The contents of
|     	that file is the elisp that fills the new variable
|     	`org-publish-cache'.  The cache file is named according to the
|     	project with `.cache' added and lives in
|     	`org-timestamp-directory'.
|     
|     	* org-publish.el (initialize-files-alist): This function and
|     	the variable `org-publish-files-alist' are not used anymore in
|     	favour of the reloadable cache and the functions for handling
|     	it. Removed therefor.
|  
|         ...
| 
`----

(hence the cc: to Sebastian). Either the function will have to be put
back, or the calls to the function in org-protocol.el will have to be
replaced by something else.

Nick

  reply	other threads:[~2010-06-30  3:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-29 22:45 Org-jekyll - org-publish-initialize-files-alist Nathan Neff
2010-06-30  3:27 ` Puneeth
2010-06-30  3:49   ` Nick Dokos [this message]
2010-06-30 11:32 ` Sebastian Rose
2010-06-30 11:45 ` Sebastian Rose
2010-06-30 14:27   ` Nathan Neff
2010-06-30 19:04     ` Sebastian Rose
2010-07-02 14:25       ` Juan Reyero

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=11902.1277869744@gamaville.dokosmarshall.org \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=punchagan@gmail.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).