From: Adam Porter <adam@alphapapa.net>
To: emacs-orgmode@gnu.org
Subject: Re: verbatim =[[link]]= and code ~[[link]]~ render as links
Date: Tue, 08 Aug 2017 11:06:54 -0500 [thread overview]
Message-ID: <87r2wmm4bl.fsf@alphapapa.net> (raw)
In-Reply-To: CAFyQvY1MHnYH6NMaqyuuwbWbgUokaXG39tBhfUp86zeES6RfEQ@mail.gmail.com
Kaushal Modi <kaushal.modi@gmail.com> writes:
> Are you referring to:
>
> [[https://www.example.com][=verbatim link descr=]]
>
> ?
Well, here's what I've noticed:
+ [[https://www.example.com][=verbatim link descr=]]
- Renders in the Emacs buffer as a link, colored as a link rather than
a code block, with visible =description=.
- Exports to HTML as <a...><code>...</code></a>, which looks fine
- Renders on GitHub as <a...>=description=</a>, which is incorrect
+ =[[https://www.example.com][verbatim link descr]]=
- Renders in the Emacs buffer as a link with the same color as other
=code= blocks.
- Exports to HTML as <code>[[https://www.example.com][verbatim link
descr]]</code>, which I guess makes sense.
- Renders on GitHub as <code>[[https://www.example.com][verbatim link
descr]]</code>, which is consistent.
So maybe Wolfram is right here, and the the problems are with the way
the ...[=description=]] links are rendered in Emacs and on GitHub.
next prev parent reply other threads:[~2017-08-08 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1145586952.1831161.1502199551475.ref@mail.yahoo.com>
2017-08-08 13:39 ` verbatim =[[link]]= and code ~[[link]]~ render as links Wolfram Volpi
2017-08-08 15:06 ` Adam Porter
2017-08-08 15:35 ` Kaushal Modi
2017-08-08 16:06 ` Adam Porter [this message]
2017-08-08 17:27 ` Kaushal Modi
[not found] <1686732720.791601.1502323347465.ref@mail.yahoo.com>
2017-08-10 0:02 ` Wolfram Volpi
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=87r2wmm4bl.fsf@alphapapa.net \
--to=adam@alphapapa.net \
--cc=emacs-orgmode@gnu.org \
/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).