emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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 10:43:40 +0100	[thread overview]
Message-ID: <CALn3zojXz_ZWD9wwDt+yiYcUYuj7wzUhwJ584xnD5AY4YABesg@mail.gmail.com> (raw)
In-Reply-To: <87eh33s9ag.fsf@gmail.com>

Hi Nicolas

On Sun, Feb 16, 2014 at 10:20 AM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
> If we leave it as-is, documentation needs to be updated anyway.
>
> If we do change them, it should only happen in "org-element.el". I don't
> think that would break existing documents, as code and verbatim are
> really close to each other.
>
> I don't care either way. Though, I lean towards the first option, as
> I like "=" as verbatim (which may be the source of the initial
> confusion).

When I read org-element-text-markup-successor

    ((equal marker "~") 'code)
    ((equal marker "=") 'verbatim)

it confuses me because of the well known Org manual

    You can make words *bold*, /italic/, _underlined_, =code= and
    ~verbatim~

Michael

  reply	other threads:[~2014-02-16  9:43 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 [this message]
2014-02-16 10:00         ` Nicolas Goaziou
2014-02-16 11:52           ` Michael Brand
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=CALn3zojXz_ZWD9wwDt+yiYcUYuj7wzUhwJ584xnD5AY4YABesg@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).