From mboxrd@z Thu Jan 1 00:00:00 1970 From: "ZHUO QL (KDr2)" Subject: Re: Proposal: references from code to text. Date: Wed, 16 May 2018 07:04:35 +0000 (UTC) Message-ID: <408787171.1793110.1526454275347@mail.yahoo.com> References: <800808596.465327.1526131788117.ref@mail.yahoo.com> <800808596.465327.1526131788117@mail.yahoo.com> <871seebxdt.fsf@gmail.com> <385386647.1304827.1526359774932@mail.yahoo.com> <87wow5s0a4.fsf@gmail.com> Reply-To: "ZHUO QL \(KDr2\)" Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1793109_1708185262.1526454275345" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41302) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fIqUR-00016i-Ho for emacs-orgmode@gnu.org; Wed, 16 May 2018 03:04:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fIqUM-0003iS-Jz for emacs-orgmode@gnu.org; Wed, 16 May 2018 03:04:47 -0400 Received: from sonic306-19.consmr.mail.gq1.yahoo.com ([98.137.68.82]:40518) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fIqUM-0003hc-Bf for emacs-orgmode@gnu.org; Wed, 16 May 2018 03:04:42 -0400 In-Reply-To: <87wow5s0a4.fsf@gmail.com> 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: Eric S Fraga Cc: Emacs-org List , John Kitchin ------=_Part_1793109_1708185262.1526454275345 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Oh, that makes sense. So in this way, we must put the text into quotes, and then into a txt code = block. And also we don't have a chance to do any transformation of the text= (e.g. org-mode list to=C2=A0javadoc format).=C2=A0=C2=A0 I think the direct reference from code to text is better. I will try to imp= lement=C2=A0it, but I'm not very familiar=C2=A0with the code base and don't= have much time, so I can't give any commitment. But once I have anything t= o show, I'll be back here=C2=A0 :) Greetings. ZHUO QL (KDr2, http://kdr2.com) =20 On Tuesday, May 15, 2018, 6:05:31 PM GMT+8, Eric S Fraga wrote:=20 =20 On Tuesday, 15 May 2018 at 04:49, ZHUO QL (KDr2) wrote: > 2. The bug Eric just found while putting a <> link within > quotes, although, it may be easy to fix.=C2=A0 I realised afterwards that it is not a bug but is a feature: org assumes that anything before the << start of the link should be repeated on each line of the incorporated src block.=C2=A0 This allows for easy incorporatio= n of code into a comment block, e.g. for C or sh etc. --=20 Eric S Fraga via Emacs 27.0.50, Org release_9.1.6-591-gee336b =20 ------=_Part_1793109_1708185262.1526454275345 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
Oh, that makes sense.

So in this way, we must put the text into quotes, and then into a txt code block. And also we don't have a chance to do any transformation of the text(e.g. org-mode list to javadoc format).  

I think the direct reference from code to text is better. I will try to implement it, but I'm not very familiar with the code base and don't have much time, so I can't give any commitment. But once I have anything to show, I'll be back here  :)

Greetings.

ZHUO QL (KDr2, http://kdr2.com)



On Tuesday, May 15, 2018, 6:05:31 PM GMT+8, Eric S Fraga <esflists@gmail.com> wrote:


On Tuesday, 15 May 2018 at 04:49, ZHUO QL (KDr2) wrote:

> 2. The bug Eric just found while putting a <> link within
> quotes, although, it may be easy to fix. 


I realised afterwards that it is not a bug but is a feature: org assumes
that anything before the << start of the link should be repeated on each
line of the incorporated src block.  This allows for easy incorporation
of code into a comment block, e.g. for C or sh etc.

--
Eric S Fraga via Emacs 27.0.50, Org release_9.1.6-591-gee336b
------=_Part_1793109_1708185262.1526454275345--