emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: emacs-orgmode@gnu.org
Subject: Re: A problem with publishing
Date: Fri, 28 Mar 2014 05:44:00 +0100	[thread overview]
Message-ID: <20140328054400.20eeb395@aga-netbook> (raw)
In-Reply-To: <5f8833325ea105e503065127806f4be8@mail.rickster.com>

Dnia 2014-03-26, o godz. 09:26:15
Rick Frankel <rick@rickster.com> napisał(a):

> On 2014-03-23 17:01, Marcin Borkowski wrote:
> > Hi list,
> > 
> > publishing doesn't work.  I guess that I broke something;).  May the
> > source and publishing directories be the same?  I have this in my
> > init.el:
> > 
> > (setq org-publish-project-alist
> > '(("fnis2014"
> > 	:base-directory "~/directory"
> > 	:publishing-directory "~/directory"
> > 	:base-extension "org\\|css\\|jpg\\|png"
> > 	:publishing-function org-reveal-export-to-html
> > 	:completion-function (lambda () (compile "make install")))))
> > 
> > The "make install" means just rsync'ing to a remote server.
> > 
> > When I "export" (C-c C-e R R) and then "publish" (C-c C-e P x) (or
> > "M-x compile"), everything is ok.  When I just "publish", changes
> > seem not to be pushed to the remote server, and I'm left with some
> > *Org export* process buffers.
> 
> My guess is that using *-export-to-html as the publishing function is
> the culprit. There should/needs to be an org-reveal-publish-to-html
> publishing function. I'm guessing the reason it works when you
> manually export is that since the html file is up-to-date vis. the org
> source, the code path bypasses that step (and just runs the completion
> function).
> 
> If org-reveal doesn't have a publishing function, try (not tested):
> 
> (lambda (plist filename pubdir)
> (org-publish-org-to 'reveal filename ".html" plist pubdir))

Thanks, I'll try it!

> BTW, org-publish has built-in support for pushing to a remote server.
> You can use a tramp url as the publishing-directory, bypassing the
> completion function.

I know, but I read in the manual that it may not be the fastest thing
in the world.  (In fact, I use a very simple Makefile, which in turn
uses rsync, so it /might/ indeed be faster, not copying unnecessary
stuff.  Not sure whether Emacs+Tramp would do it.)

> rick

Thanks again,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University

next prev parent reply	other threads:[~2014-03-28  4:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-23 21:01 A problem with publishing Marcin Borkowski
2014-03-26 13:26 ` Rick Frankel
2014-03-28  4:44   ` Marcin Borkowski [this message]
2014-03-28 14:52     ` Rick Frankel

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=20140328054400.20eeb395@aga-netbook \
    --to=mbork@wmi.amu.edu.pl \
    --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

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