emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: fredtantini@free.fr
To: "Charles C. Berry" <ccberry@ucsd.edu>
Cc: fredtantini@free.fr, "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Fxporting a new markup
Date: Sun, 10 Apr 2016 10:00:59 +0200	[thread overview]
Message-ID: <1460275259.570a083b2ecca@imp.free.fr> (raw)
In-Reply-To: <alpine.OSX.2.20.1604090934280.711@charles-berrys-macbook.local>

Thanks!

I don't know if it was right in front of me or if I didn't look at the right
files, but as it was indicated in the commit and in org-element.el:

> ;; Creating a new type of object requires to alter
> ;; `org-element--object-regexp' and `org-element--object-lex', add the
> ;; new type in `org-element-all-objects', and possibly add
> ;; restrictions in `org-element-object-restrictions'.

So I did, and my export works now. A big thanks for showing me the right way!

--
Fred

Quoting "Charles C. Berry" <ccberry@ucsd.edu>:

> On Sat, 9 Apr 2016, fredtantini@free.fr wrote:
>
> > Hi everyone,
> >
> > I need your help.
> >
> > Prior to version 8.3.* I used a custom marker (&#8240;) to export keyboard
> > shortcut in html (that is to kbd tags). What I have done is, in ox-org.el
> or
> > org-element.el, every time there was a function with "bold" or "code",
> > I copied/pasted the function and modified it to meet my needs.
> > For instance, I have created a
> =org-element-my-object-keystroke-interpreter=
> > function, or override the =org-element-object-successor-alist= const.
> >
> > I have detailed what I have done in this emacs.stackexchange answer:
> >
>
http://emacs.stackexchange.com/questions/12814/extending-org-mode-with-more-markups/12822#12822
> >
> > My setup works great with org versions &#8804;8.2.10, but with 8.3.1 (to
> 8.3.4),
> > it doesn't do the job&#8230; I have tried to edebug, and looked at commits,
> but
> > I can't pinpoint what's the problem. The Release notes doesn't seem either
> to
> > indicate that there was a change between the versions that could broke my
> > workflow :(
> >
> > What have I missed?
>
> There is no `org-element-object-successor-alist'. You need to look two
> years back in the commits:
>
> bash-3.2$ git log -Sorg-element-object-successor
>
>    commit b5dd32c7e49f3125e5541e85197b8e83e34739a6
>    Author: Nicolas Goaziou <n.goaziou@gmail.com>
>    Date:   Thu Mar 27 00:04:04 2014 +0100
>
>    org-element: Rewrite object parsing algorithm
>
>    * lisp/org-element.el (org-element-all-successors,
>    org-element-object-successor-alist): Remove variables.
>    [...]
>
> HTH,
>
> Chuck
>

  reply	other threads:[~2016-04-10  8:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-09 11:24 Fxporting a new markup fredtantini
2016-04-09 16:40 ` Charles C. Berry
2016-04-10  8:00   ` fredtantini [this message]
2016-04-09 19:00 ` Adam Porter
2016-04-09 22:41   ` Adam Porter

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=1460275259.570a083b2ecca@imp.free.fr \
    --to=fredtantini@free.fr \
    --cc=ccberry@ucsd.edu \
    --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
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).