From: Kaushal Modi <kaushal.modi@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>, Rasmus <rasmus@gmx.us>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: [RFC] New "kbd" macro?
Date: Fri, 15 Sep 2017 13:08:57 +0000 [thread overview]
Message-ID: <CAFyQvY0aoMjc6qTYtKnJimiGA0E-eF+z43X_V7KqvmH-6m_wcg@mail.gmail.com> (raw)
In-Reply-To: <CAFyQvY1c27R41FHjQrdg0ZOAqNPUV115TsiYKpm4MQg6Lb4qAw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
On Fri, Sep 15, 2017, 8:54 AM Kaushal Modi <kaushal.modi@gmail.com> wrote:
> On Thu, Sep 14, 2017 at 6:03 PM Nicolas Goaziou <mail@nicolasgoaziou.fr>
> wrote:
>
>>
>> > - HTML, MD :: as Kaushal points out, please use <kbd>.</kbd>.
>>
>> This is (almost) already the case.
>>
>
> Thanks. I tried the second version of the patch and it works great. About
> the /almost/, the same <kbd>..</kbd> export worked for MD exports too.. as
> ox-md is derived from ox-html, and also as all Markdown renderers allow
> inline HTML.
>
Makes me think.. instead of hard-codng the kbd export forms in the macro,
wouldn't it be better to define those in the respective exporter backends?
That way I can easily override the behavior I want using :translate-alist
in my custom backend.
Can a mechanism be put in place so that we can have a 'kbd' element
behavior that can be defined in the :translate-alist?
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 1705 bytes --]
next prev parent reply other threads:[~2017-09-15 13:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 13:22 [RFC] New "kbd" macro? Nicolas Goaziou
2017-09-13 14:03 ` Kaushal Modi
2017-09-13 14:05 ` Kaushal Modi
2017-09-13 19:25 ` Nicolas Goaziou
2017-09-14 4:45 ` Marcin Borkowski
2017-09-14 13:49 ` Oleh Krehel
2017-09-13 19:24 ` Eric S Fraga
2017-09-14 8:07 ` Rasmus
2017-09-14 22:02 ` Nicolas Goaziou
2017-09-15 7:36 ` Rasmus
2017-09-15 10:16 ` Nicolas Goaziou
2017-09-15 11:20 ` Rasmus
2017-09-15 11:52 ` Nicolas Goaziou
2017-09-15 12:54 ` Kaushal Modi
2017-09-15 13:08 ` Kaushal Modi [this message]
2017-09-15 15:53 ` Nicolas Goaziou
2017-09-17 7:20 ` Nicolas Goaziou
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=CAFyQvY0aoMjc6qTYtKnJimiGA0E-eF+z43X_V7KqvmH-6m_wcg@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=rasmus@gmx.us \
/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).