From: "Berry, Charles" <ccberry@ucsd.edu>
To: Jens Lechtenboerger <lechten@wi.uni-muenster.de>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Key bindings for Org export back-ends?
Date: Sat, 9 Feb 2019 00:31:07 +0000 [thread overview]
Message-ID: <705BA781-8F31-4783-8263-EF20A3AE16DB@ucsd.edu> (raw)
In-Reply-To: <87va1u3ctf.fsf@informationelle-selbstbestimmung-im-internet.de>
> 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.
next prev parent reply other threads:[~2019-02-09 0:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 8:27 Key bindings for Org export back-ends? Jens Lechtenboerger
2019-02-08 11:51 ` Kaushal Modi
2019-02-08 14:02 ` Jens Lechtenboerger
2019-02-08 15:18 ` Jens Lechtenboerger
2019-02-09 0:31 ` Berry, Charles [this message]
2019-02-09 1:20 ` John Kitchin
2019-02-09 5:29 ` Berry, Charles
-- strict thread matches above, loose matches on Subject: below --
2019-02-08 15:48 Thomas S. Dye
2019-02-08 15:54 ` Kaushal Modi
2019-02-08 21:03 ` Jens Lechtenboerger
2019-02-09 16:40 ` Jens Lechtenboerger
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=705BA781-8F31-4783-8263-EF20A3AE16DB@ucsd.edu \
--to=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=lechten@wi.uni-muenster.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.