From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Thomas S. Dye" <tsdye.com@gmail.com>
Subject: Re: typo, sp at C++ Source Code Blocks in Org Mode
Date: Sat, 10 Nov 2018 06:45:01 -1000
Message-ID: <1541868301.4541.0@smtp.gmail.com>
References: <1541782329.10143.0@smtp.gmail.com>
	<B8684E20-8DB5-476F-8596-9E621152F1F9@scratch.space>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=-JkFLhpLWV93ICH/QBStt"
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([208.118.235.92]:36857)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <tsdye.com@gmail.com>) id 1gLWOH-0003Iy-KV
	for emacs-orgmode@gnu.org; Sat, 10 Nov 2018 11:45:48 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <tsdye.com@gmail.com>) id 1gLWNf-0006gW-44
	for emacs-orgmode@gnu.org; Sat, 10 Nov 2018 11:45:10 -0500
Received: from mail-pf1-x42e.google.com ([2607:f8b0:4864:20::42e]:38701)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <tsdye.com@gmail.com>) id 1gLWNe-0006g1-Si
	for emacs-orgmode@gnu.org; Sat, 10 Nov 2018 11:45:07 -0500
Received: by mail-pf1-x42e.google.com with SMTP id b11-v6so2321640pfi.5
	for <emacs-orgmode@gnu.org>; Sat, 10 Nov 2018 08:45:06 -0800 (PST)
In-Reply-To: <B8684E20-8DB5-476F-8596-9E621152F1F9@scratch.space>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode/>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: Van L <van@scratch.space>
Cc: emacs-org list <emacs-orgmode@gnu.org>

--=-JkFLhpLWV93ICH/QBStt
Content-Type: text/plain; charset=us-ascii; format=flowed

Aloha Van L,


On Sat, Nov 10, 2018 at 12:17 AM, Van L <van@scratch.space> wrote:
> 
>>  AFAIK there is no mechanism to have changes in  one propagate 
>> changes in the other.
> 
> It should be possible to link the two because both are org files.
> 
> Worg would need to render to info:worg.

That's an interesting idea.  AFAICT it should be possible.  
Nevertheless, my guess is that it would be a lot of work to mark up the 
Worg sources to get well-formatted info output.

All the best,
Tom

--=-JkFLhpLWV93ICH/QBStt
Content-Type: text/html; charset=us-ascii

<div id="geary-body"><div>Aloha Van L,</div><div><br></div></div><div id="geary-quote"><br>On Sat, Nov 10, 2018 at 12:17 AM, Van L &lt;van@scratch.space&gt; wrote:<br><blockquote type="cite"><div class="plaintext" style="white-space: pre-wrap;">
<blockquote> AFAIK there is no mechanism to have changes in  one propagate changes in the other.
</blockquote>
It should be possible to link the two because both are org files. 

Worg would need to render to info:worg.</div></blockquote><span style="white-space: pre-wrap;"><br></span><div><span style="white-space: pre-wrap;">That's an interesting idea.  AFAICT it should be possible.  Nevertheless, my guess is that it would be a lot of work to mark up the Worg sources to get well-formatted info output. </span></div><div><span style="white-space: pre-wrap;"><br></span></div><div><span style="white-space: pre-wrap;">All the best,</span></div><div><span style="white-space: pre-wrap;">Tom</span></div></div>
--=-JkFLhpLWV93ICH/QBStt--