emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Bastien <bzg@gnu.org>
To: Michael Brand <michael.ch.brand@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>, Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: parser: verbatim or code?
Date: Tue, 04 Mar 2014 10:52:11 +0100	[thread overview]
Message-ID: <87lhwq44wu.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CALn3zoh-Wsfpmun5rtsx-gWNmHmHbL=rwTnHh34f1XaBABNmgA@mail.gmail.com>	(Michael Brand's message of "Sun, 16 Feb 2014 12:52:10 +0100")

Hi Yasushi, Michael and Nicolas,

Michael Brand <michael.ch.brand@gmail.com> 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.

Thanks,

-- 
 Bastien

next prev parent reply	other threads:[~2014-03-04 10:47 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
2014-03-04  9:52             ` Bastien [this message]
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=87lhwq44wu.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=michael.ch.brand@gmail.com \
    --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

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).