From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Moe Subject: Re: Exporting comments to comments? Date: Sun, 23 Feb 2020 21:41:42 +0100 Message-ID: <87d0a5t4s9.fsf@christianmoe.com> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:55655) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j5yIX-000055-C2 for emacs-orgmode@gnu.org; Sun, 23 Feb 2020 15:56:22 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j5yIW-0004IX-8e for emacs-orgmode@gnu.org; Sun, 23 Feb 2020 15:56:21 -0500 Received: from mailer-211-145.hitrost.net ([91.185.211.145]:10555) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1j5yIW-0004BR-27 for emacs-orgmode@gnu.org; Sun, 23 Feb 2020 15:56:20 -0500 In-reply-to: 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-mx.org@gnu.org Sender: "Emacs-orgmode" To: "Allen S. Rout" Cc: emacs-orgmode@gnu.org I use a rather complex comment macro to make ODT annotations without introducing unwanted paragraph breaks. I'm not sure what the Markdown comment syntax is. But e.g. for HTML, the macro could be defined as simply as: #+MACRO: comment @@html:@@ Then you can write things like This is a sentence with a comment.{{{comment(This is the comment.)}}} This is another sentence. and get comments in the exported HTML. It's ugly, and any commas within the comment text must be backslash-escaped, but it works, and could be adapted for Markdown. HTH, Christian Allen S. Rout writes: > I'd like to write an org-mode document, export it to markdown, and have > comments exist in the markdown. > > > I feel like I'm thinking about the process incorrectly, and it's hard to > search around because the discussions around 'org-mode comments' focus > on org data for which authors would like to _prevent_ export. > > I saw some old conversations about making links to the hacked-in > comment: URI scheme, but that seemed quite hackish indeed. > > I thought about making a block of a 'comment' type, but of course all > the workflow for that is, again, focused on either preventing its export > in the first place, or making sure that it's exported in a visible > manner in the output. ("I want to print the comments in my LaTeX.."). > > > So... am I missing something obvious? Anyone else trying something similar? > > > - Allen S. Rout