From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastien Vauban Subject: Re: parser: verbatim or code? Date: Fri, 23 Jan 2015 12:33:18 +0100 Message-ID: <86y4otn341.fsf@example.com> References: <87iosg1oge.wl@dns1.atmark-techno.com> <87mwhsfo9e.fsf@gmail.com> <87ob27tp8p.wl@dns1.atmark-techno.com> <87eh33s9ag.fsf@gmail.com> <87a9drs7gj.fsf@gmail.com> <87lhwq44wu.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain Return-path: 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-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: Bastien , Michael Brand , Nicolas Goaziou Cc: Org Mode Hello, Bastien wrote: > Hi Yasushi, Michael and Nicolas, > > Michael Brand writes: >> The syntax for inline code snippets seems easier to read by human and >> to parse with "~" than with "=" because inline code snippets use "~" >> less often than "=". I avoid "~/" by using "$HOME/" in my notes about >> shell and shell scripts. Some examples: > > I've now fix those inconsistencies, both in the manual and in the > code. I followed Michael suggestion to use ~code~ and =verbatim=. > > We may need to update the way export backend treat this markup, and > try to be consistent here too. Since = and ~ have been inverted, I think it'd make sense to make `org-babel-inline-result-wrap' now default to "~%s" (instead of "=%s"), for markup that produces verbatim text. That will put fix back as what they were for people having different CSS or LaTeX styles applied to both markers. Best regards, Seb -- Sebastien Vauban