From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Brand Subject: Re: parser: verbatim or code? Date: Sun, 16 Feb 2014 12:52:10 +0100 Message-ID: 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> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58478) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WF0Ga-0000gJ-2E for emacs-orgmode@gnu.org; Sun, 16 Feb 2014 06:52:12 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WF0GZ-0005xr-9S for emacs-orgmode@gnu.org; Sun, 16 Feb 2014 06:52:11 -0500 Received: from mail-qc0-x235.google.com ([2607:f8b0:400d:c01::235]:65011) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WF0GZ-0005xm-5B for emacs-orgmode@gnu.org; Sun, 16 Feb 2014 06:52:11 -0500 Received: by mail-qc0-f181.google.com with SMTP id e9so22577749qcy.12 for ; Sun, 16 Feb 2014 03:52:10 -0800 (PST) In-Reply-To: <87a9drs7gj.fsf@gmail.com> 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou Cc: Org Mode Hi Nicolas On Sun, Feb 16, 2014 at 11:00 AM, Nicolas Goaziou wrote: > Indeed, that's the very issue we're discussing in this thread. > > I'm not sure to understand what you mean here. For me it was not explicit enough that this ((equal marker "~") 'code) ((equal marker "=") 'verbatim) is the part discussed. I am not sure if it is that simple but just from the word "code" and from the usage on Worg I tend to conclude that for inline code snippets 'code should be preferred and 'verbatim only be used for non-code things more similar to just like an inline quote. Only if this distinction should really matter then keeping the above code unchanged and changing the Org manual from =code= ~verbatim~ to ~code~ =verbatim= would have the following advantage: 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: Bla ~a = 1~ bla, bla ~b=2~ bla, bla ~local my_variable= # Bash shell: Set to empty value.~ bla, bla ~source $HOME/.profile~ bla. vs. Bla =a = 1= bla, bla =b=2= bla, bla =local my_variable= # Bash shell: Set to empty value.= bla, bla =source $HOME/.profile= bla. Michael