From: Van L <van@scratch.space>
To: "Thomas S. Dye" <tsdye.com@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: typo, sp at C++ Source Code Blocks in Org Mode
Date: Sat, 10 Nov 2018 21:17:30 +1100 [thread overview]
Message-ID: <B8684E20-8DB5-476F-8596-9E621152F1F9@scratch.space> (raw)
In-Reply-To: <1541782329.10143.0@smtp.gmail.com>
> 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.
next prev parent reply other threads:[~2018-11-10 10:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 16:52 typo, sp at C++ Source Code Blocks in Org Mode Thomas S. Dye
2018-11-10 10:17 ` Van L [this message]
2018-11-10 16:45 ` Thomas S. Dye
2018-11-14 13:29 ` Van L
-- strict thread matches above, loose matches on Subject: below --
2018-11-05 15:57 Thomas S. Dye
2018-11-09 15:03 ` Van L
2018-11-05 8:00 Van L
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=B8684E20-8DB5-476F-8596-9E621152F1F9@scratch.space \
--to=van@scratch.space \
--cc=emacs-orgmode@gnu.org \
--cc=tsdye.com@gmail.com \
/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).