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

From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Yasushi SHOJI <yashi@atmark-techno.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: parser: verbatim or code?
Date: Sun, 16 Feb 2014 10:20:55 +0100	[thread overview]
Message-ID: <87eh33s9ag.fsf@gmail.com> (raw)
In-Reply-To: <87ob27tp8p.wl@dns1.atmark-techno.com> (Yasushi SHOJI's message of "Sun, 16 Feb 2014 17:51:02 +0900")

Hello,

Yasushi SHOJI <yashi@atmark-techno.com> writes:

> Nick Dokos wrote:
>> 
>> I think it's a code bug: ~verbatim~ is the precedent-setting latex
>> convention.
>> 
>> However fixing it might break existing documents (although in many
>> instances code and verbatim are treated equivalently, so that might
>> not be much of a problem).
>
> A quick grep on export back-ends reveals that some back-ends uses them
> differently. Namely
>
>  - latex
>  - man
>  - org ;-)
>  - texinfo
>
> Should I just leave as-is?

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


Regards,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2014-02-16  9:20 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 [this message]
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
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=87eh33s9ag.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yashi@atmark-techno.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).