From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kaushal Modi Subject: Re: verbatim =[[link]]= and code ~[[link]]~ render as links Date: Tue, 08 Aug 2017 17:27:44 +0000 Message-ID: References: <1145586952.1831161.1502199551475.ref@mail.yahoo.com> <1145586952.1831161.1502199551475@mail.yahoo.com> <87fud2nlp9.fsf@alphapapa.net> <87r2wmm4bl.fsf@alphapapa.net> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a113e8452b24f940556414890" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59198) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1df8IR-0001Yk-8y for emacs-orgmode@gnu.org; Tue, 08 Aug 2017 13:28:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1df8IP-0006Pf-TD for emacs-orgmode@gnu.org; Tue, 08 Aug 2017 13:27:59 -0400 Received: from mail-lf0-x236.google.com ([2a00:1450:4010:c07::236]:36326) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1df8IP-0006P3-Kx for emacs-orgmode@gnu.org; Tue, 08 Aug 2017 13:27:57 -0400 Received: by mail-lf0-x236.google.com with SMTP id o85so17821582lff.3 for ; Tue, 08 Aug 2017 10:27:57 -0700 (PDT) In-Reply-To: <87r2wmm4bl.fsf@alphapapa.net> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Adam Porter , emacs-org list --001a113e8452b24f940556414890 Content-Type: text/plain; charset="UTF-8" On Tue, Aug 8, 2017, 1:02 PM Adam Porter 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 --001a113e8452b24f940556414890 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Aug 8, 2017, 1:02 PM Ad= am Porter <adam@alphapapa.net&= gt; wrote:


Well, here's what I've noticed:

My observations have been the same. I strongly believe that GitHub n= eeds to fix their parsing of Org verbatim/code text.=C2=A0

Here's another similar problem with GitHub rendering Org verba= tim, in tables:=C2=A0https://github.com/kaushalmodi/ox-hugo/blob/= master/README.org#formatting

Note the =3D=3Dmo= nospace=3D=3D text in the table.=C2=A0

So maybe Wolfram is right here, a= nd the the problems are with the way
the ...[=3Ddescription=3D]] links are rendered in Emacs and on GitHub.
<= /blockquote>

Yup. Another reason to believe so is = that=C2=A0

[[h= ttps://www.example.com][=3Ddescription=3D]]

is= equivalent to

[`description`](https://www.example.com)

in M= arkdown,=C2=A0and GitHub renders the Markdow= n version fine.

=
Also, below won't be rendered= as a link :)

`[description](https://www.example.com)`
--

Kaushal Modi

--001a113e8452b24f940556414890--