From: Jens Lechtenboerger <lechten@wi.uni-muenster.de>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>,
"Thomas S. Dye" <tdye@hawaii.edu>
Subject: Re: Key bindings for Org export back-ends?
Date: Sat, 09 Feb 2019 17:40:42 +0100 [thread overview]
Message-ID: <87o97kkj91.fsf@informationelle-selbstbestimmung-im-internet.de> (raw)
In-Reply-To: <87sgwygfgm.fsf@informationelle-selbstbestimmung-im-internet.de> (Jens Lechtenboerger's message of "Fri, 8 Feb 2019 22:03:53 +0100")
On 2019-02-08, at 22:03, Jens Lechtenboerger wrote:
> On 2019-02-08, at 10:54, Kaushal Modi wrote:
>
>> On Fri, Feb 8, 2019 at 10:48 AM Thomas S. Dye <tdye@hawaii.edu> wrote:
>>
>>> One place for the list of key bindings might be here:
>>> https://orgmode.org/worg/exporters/index.html
>>>
>>
>> That's a great idea! How about creating a single Org table with columns
>> like Name, Description, Binding, Core/Contributed, and then sort the rows
>> by the Binding column?
>>
>> We can leave the obsolete exporters section separate as it is right now.
>
> Should the description really go into a table? Or might the table
> just provide an overview before the current section “Core
> exporters”?
Actually, a similar table exists, marked as in progress:
https://orgmode.org/worg/exporters/ox-overview.html
Column “Worg Tutorial” is mostly empty. Column “Org-mode Manual”
only contains entries for the upper half. Should we combine both
into one, “Tutorial/Manual”?
Or is such a table a futile goal given the potential amount of
back-ends pointed out by Chuck in a parallel answer?
Best wishes
Jens
next prev parent reply other threads:[~2019-02-09 16:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 15:48 Key bindings for Org export back-ends? Thomas S. Dye
2019-02-08 15:54 ` Kaushal Modi
2019-02-08 21:03 ` Jens Lechtenboerger
2019-02-09 16:40 ` Jens Lechtenboerger [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-08 8:27 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
2019-02-09 1:20 ` John Kitchin
2019-02-09 5:29 ` Berry, Charles
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=87o97kkj91.fsf@informationelle-selbstbestimmung-im-internet.de \
--to=lechten@wi.uni-muenster.de \
--cc=emacs-orgmode@gnu.org \
--cc=kaushal.modi@gmail.com \
--cc=tdye@hawaii.edu \
/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).