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

From: Bastien <bzg@gnu.org>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Emacs Org mode <emacs-orgmode@gnu.org>
Subject: Re: Worg publishing issue
Date: Wed, 13 Feb 2013 11:45:30 +0100	[thread overview]
Message-ID: <87ip5wwkwo.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87txpol2ev.fsf@gmail.com> (Nicolas Goaziou's message of "Thu, 07 Feb 2013 13:43:52 +0100")

Hi Nicolas,

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Bastien <bzg@altern.org> writes:
>
>> 2 problems, a trivial one and a let's-prepare-for-headache one:
>>
>> 1. `org-publish-org-to-html' does not exist in the new export/publish
>>     libraries -- Nicolas, would that be enough to have aliases here
>>     (from org-publish-org-to-html to org-html-publish-to-html)?  I
>>     guess many people rely on thse org-publish-org-to* functions.
>
> Publishing functions have been moved into their respective back-end.
> That way, ox-publish.el doesn't have to know about every back-end
> defined.

Thanks -- so that's not a problem for Worg, which uses Org from the
maint branch for publishing.  I've just fixed the bug in maint that
prevented Worg from publishing correctly.

> It's not very clean, but you can probably define aliases in
> ox-publish.el, since real publishing functions should be autoloaded
> anyway. If you do so, I suggest to, at least, provide a deprecation
> notice.*

I don't plan to add those aliases, let's move forward and add the
deprecation notice in the 8.0 release announcement (and on Worg.)

Thanks,

-- 
 Bastien

next prev parent reply	other threads:[~2013-02-13 10:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06 13:19 Worg publishing issue Suvayu Ali
2013-02-06 15:26 ` Nick Dokos
2013-02-07  8:42 ` Bastien
2013-02-07  9:35   ` Suvayu Ali
2013-02-13 17:32     ` Bastien
2013-02-13 19:37       ` Suvayu Ali
2013-02-07 12:43   ` Nicolas Goaziou
2013-02-13 10:45     ` Bastien [this message]
2013-02-08 22:54 ` Suvayu Ali
2013-02-08 23:35   ` Thorsten Jolitz
2013-02-08 23:39   ` Thorsten Jolitz

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=87ip5wwkwo.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@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

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