From: Kaushal Modi <kaushal.modi@gmail.com>
To: Adam Porter <adam@alphapapa.net>, emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: verbatim =[[link]]= and code ~[[link]]~ render as links
Date: Tue, 08 Aug 2017 17:27:44 +0000 [thread overview]
Message-ID: <CAFyQvY27wSAxk0NvEAt_mFzJoXUzacESucnPo5dHWS-XRLFP+g@mail.gmail.com> (raw)
In-Reply-To: <87r2wmm4bl.fsf@alphapapa.net>
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
On Tue, Aug 8, 2017, 1:02 PM Adam Porter <adam@alphapapa.net> wrote:
>
>
> Well, here's what I've noticed:
>
My observations have been the same. I strongly believe that GitHub needs to
fix their parsing of Org verbatim/code text.
Here's another similar problem with GitHub rendering Org verbatim, in
tables:
https://github.com/kaushalmodi/ox-hugo/blob/master/README.org#formatting
Note the ==monospace== text in the table.
So maybe Wolfram is right here, and the the problems are with the way
> the ...[=description=]] links are rendered in Emacs and on GitHub.
>
Yup. Another reason to believe so is that
[[https://www.example.com][=description=]]
is equivalent to
[`description`](https://www.example.com)
in Markdown, and GitHub renders the Markdown version fine.
Also, below won't be rendered as a link :)
`[description](https://www.example.com)`
> --
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 2170 bytes --]
next prev parent reply other threads:[~2017-08-08 17:28 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
2017-08-08 17:27 ` Kaushal Modi [this message]
[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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFyQvY27wSAxk0NvEAt_mFzJoXUzacESucnPo5dHWS-XRLFP+g@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=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 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.