Re: Key bindings for Org export back-ends?

[John Kitchin <jkitchin@andrew.cmu.edu>]

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

my goto solution to keymap collisions is hydra. Here is one that shows how
to make one for exporting in org-mode:

https://github.com/abo-abo/hydra/blob/master/hydra-ox.el


John

-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu



On Fri, Feb 8, 2019 at 7:32 PM Berry, Charles <ccberry@ucsd.edu> wrote:

>
>
> > On Feb 8, 2019, at 12:27 AM, Jens Lechtenboerger <
> lechten@wi.uni-muenster.de> wrote:
> >
> > Hi there,
> >
> > I need to assign a key to an Org export back-end.  My first attempt
> > ended in a conflict, so I’d like to collect a (full?) list.
> >
>
> I'm not trolling, but ...
>
> There are about 30 packages on melpa.
>
> And doing a search on GitHub:
>
> `org-export-define-derived-backend  extension:.el language:"Emacs Lisp"'
>
> gave me over 9000 (!) results.
>
> And  `org-export-define-derived-backend extension:.org language:Org'
>
> gave me 54 more. Maybe some overlap.
>
> I am sure there are false positives. Some do not have a :menu. Some are
> copies used in init files. Some in the *.org files might just be
> commentary.
>
> But still there are a lot out there.
>
> ===
>
> Maybe a better angle is to think about how to extend the menu
> functionality to accommodate all of the possible collisions.  I'd offer to
> help in this, but I will not have any time for some weeks to come.
>
> Chuck
>
> p.s. I will go offline for a couple of weeks starting in 48 hours. So if I
> do not respond to a follow up, it is not because I am ignoring it.
>
>

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