From: Michael Brand <michael.ch.brand@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: parser: verbatim or code?
Date: Sun, 16 Feb 2014 12:52:10 +0100 [thread overview]
Message-ID: <CALn3zoh-Wsfpmun5rtsx-gWNmHmHbL=rwTnHh34f1XaBABNmgA@mail.gmail.com> (raw)
In-Reply-To: <87a9drs7gj.fsf@gmail.com>
Hi Nicolas
On Sun, Feb 16, 2014 at 11:00 AM, Nicolas Goaziou <n.goaziou@gmail.com> 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
next prev parent reply other threads:[~2014-02-16 11:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-15 13:43 parser: verbatim or code? Yasushi SHOJI
2014-02-15 14:23 ` Nick Dokos
2014-02-16 8:51 ` Yasushi SHOJI
2014-02-16 9:20 ` Nicolas Goaziou
2014-02-16 9:43 ` Michael Brand
2014-02-16 10:00 ` Nicolas Goaziou
2014-02-16 11:52 ` Michael Brand [this message]
2014-03-04 9:52 ` Bastien
2015-01-23 11:33 ` Sebastien Vauban
2015-01-23 19:20 ` Sebastien Vauban
2015-01-23 20:31 ` Aaron Ecay
[not found] ` <87egqlgrws.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-30 11:02 ` Sebastien Vauban
2014-02-18 4:19 ` Yasushi SHOJI
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='CALn3zoh-Wsfpmun5rtsx-gWNmHmHbL=rwTnHh34f1XaBABNmgA@mail.gmail.com' \
--to=michael.ch.brand@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@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).