[O] Exporting a new markup

[fredtantini]

Hi everyone,

I need your help.

Prior to version 8.3.* I used a custom marker () 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 8.2.10, but with 8.3.1 (to 8.3.4),
it doesn't do the job 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?
--
Fred

Re: [O] Fxporting a new markup

[fredtantini]

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" :

> On Sat, 9 Apr 2016, fredtant...@free.fr wrote:
>
> > Hi everyone,
> >
> > I need your help.
> >
> > Prior to version 8.3.* I used a custom marker () 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 8.2.10, but with 8.3.1 (to
> 8.3.4),
> > it doesn't do the job 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 
>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
>

[O] Fxporting a new markup

[fredtantini]

Hi everyone,

I need your help.

Prior to version 8.3.* I used a custom marker () 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 8.2.10, but with 8.3.1 (to 8.3.4),
it doesn't do the job 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?
--
Fred