emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: emacs-org list <emacs-orgmode@gnu.org>,
	larstvei@ifi.uio.no, kjambunathan@gmail.com, n.goaziou@gmail.com
Subject: Re: [ANN] Export block syntax change
Date: Wed, 6 Jan 2016 14:57:01 -0500	[thread overview]
Message-ID: <CAFyQvY35RtumVT3iUR+1oX0-j-doqHLCeKuqkmfMPtg88DTnqw@mail.gmail.com> (raw)
In-Reply-To: <877fjmtwfd.fsf@nicolasgoaziou.fr>

[-- Attachment #1: Type: text/plain, Size: 1587 bytes --]

Thanks Nicolas.

I agged the org-mode git repo for ":export-block" and found these
references:

contrib/lisp/ox-gfm.el
54:  :export-block '("GFM" "GITHUB FLAVORED MARKDOWN")

(Copied Lars for above)

contrib/lisp/ox-freemind.el
46:  :export-block "FREEMIND"

(Copied Jambunathan for above)

(And copying you for groff and org.texi)

contrib/lisp/ox-groff.el
95:  :export-block "GROFF"

doc/org.texi
17971:@code{:export-block} (to specify what blocks should not be exported
by this

doc/org
16222:dispatcher), ‘:export-block’ (to specify what blocks should not be

etc/ORG-NEWS
78:Moreover, ~:export-block~ keyword used in ~org-export-define-backend~

These references need to be removed, right?

Thanks.




--
Kaushal Modi

On Wed, Jan 6, 2016 at 1:06 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:

> Hello,
>
> Kaushal Modi <kaushal.modi@gmail.com> writes:
>
> > I believe this change is breaking the ox-twbs package.
> >
> > The error shown is:
> >
> > Debugger entered--Lisp error: (error "Unknown keyword: :export-block")
>
> [...]
>
> > The error goes away after I comment out the line with :export-block
> keyword
> > in the org-export-define-backend function call.
> >
> > Example:
> >
> https://github.com/marsmining/ox-twbs/blob/cfe67353d148e65a7676f1609d8cc22a4c8fbc78/ox-twbs.el#L108
> >
> > What would be the proposed/correct fix for this?
>
> Remove the :export-block keyword, which is no longer necessary. I'm
> going to update ORG-NEWS. Thank you.
>
> Regards,
>
> --
> Nicolas Goaziou
>

[-- Attachment #2: Type: text/html, Size: 2776 bytes --]

  reply	other threads:[~2016-01-06 19:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-20 21:06 [ANN] Export block syntax change Nicolas Goaziou
2015-12-20 23:02 ` Rasmus
2015-12-21  8:21   ` Nicolas Goaziou
2015-12-21 11:09 ` Ken Mankoff
2015-12-21 12:40   ` Nicolas Goaziou
2016-01-02  7:54 ` Suvayu Ali
2016-01-02  8:18   ` John Hendy
2016-01-02 10:54   ` Nicolas Goaziou
2016-01-02 14:40     ` Suvayu Ali
2016-01-06 16:04       ` Kaushal Modi
2016-01-06 18:06         ` Nicolas Goaziou
2016-01-06 19:57           ` Kaushal Modi [this message]
2016-01-06 21:52             ` Nicolas Goaziou
2016-01-06 22:26               ` Kaushal Modi
2016-01-11  3:56                 ` Kaushal Modi
2016-01-11  9:20                   ` Nicolas Goaziou

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=CAFyQvY35RtumVT3iUR+1oX0-j-doqHLCeKuqkmfMPtg88DTnqw@mail.gmail.com \
    --to=kaushal.modi@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kjambunathan@gmail.com \
    --cc=larstvei@ifi.uio.no \
    --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
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).