From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Charles C. Berry" Subject: Re: Multiple underscores crash org latex export; other exporters survive Date: Mon, 5 Dec 2016 09:30:16 -0800 Message-ID: References: <49b70a0c-f81b-660b-e2f5-9921ab488d65@gmail.com> <50e77033-c13c-c0be-5d4a-ec5c107e93ae@gmail.com> <87bmwsatox.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59553) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cDx5s-0005OU-61 for emacs-orgmode@gnu.org; Mon, 05 Dec 2016 12:30:25 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cDx5p-0007PR-0E for emacs-orgmode@gnu.org; Mon, 05 Dec 2016 12:30:24 -0500 Received: from iport-bcv1-out.ucsd.edu ([132.239.0.119]:13732) by eggs.gnu.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.71) (envelope-from ) id 1cDx5o-0007Oy-Ie for emacs-orgmode@gnu.org; Mon, 05 Dec 2016 12:30:20 -0500 In-Reply-To: <87bmwsatox.fsf@nicolasgoaziou.fr> 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: Nicolas Goaziou Cc: Scott Randby , emacs-orgmode@gnu.org On Sun, 4 Dec 2016, Nicolas Goaziou wrote: > Hello, > > Scott Randby writes: > >> There is an interesting issue here. I sometimes want to use ~ in a code >> snippet, so I can't use ~code snippet~. Yet, > > Indeed, this was discussed in this ML. We need some escape character in > Org. A general escape character is a bit ambitious, and not necessarily > useful, but we could introduce one specifically for verbatim and code > markers, much like in macros and verbatim blocks, e.g. > > ~some\~code\=with special\\ characters~ > > There is a design decision involved: what character can be escaped? It > could be anything, or limit to "~" for code and "=" for verbatim > markers. For example macros limit escape-able characters to "," and "\". > This makes the contents easier to read, but the rule is inconsistent. > > Thoughts? I do not think this is needed. The existing markup is simple and useful and does not complicate the appearance of the org buffer nor editting it. More complicated inline markups can be rendered with export snippets, macros, and/or inline src blocks. For example: -- #+MACRO: code src_code[:eval no :exports code]{$1} {{{code(y~x)}}} -- will handle many situations. If one needs to render something with embedded commas and/or backslashes like : y~x(z,w) : cat("here is a newline\n") then : src_code{ y~x(z,w) } : src_code{ cat("here is a newline\n") } works if `org-babel-default-header-args:code' is : '((:eval . "no")(:exports . "code")) HTH, Chuck