emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: kim.lindberger@gmail.com
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Markup border outdated in spec?
Date: Fri, 04 Sep 2020 11:43:28 +0200	[thread overview]
Message-ID: <87v9gtq3lr.fsf@gnu.org> (raw)
In-Reply-To: <0996433a0c6ab0de3433f39a0e37f57c806e16e2.camel@gmail.com> (kim lindberger's message of "Sun, 09 Aug 2020 10:59:09 +0200")

Hi Kim,

thanks for reporting this.

kim.lindberger@gmail.com writes:

> There seems to be an inconsistency between the Org syntax spec and the
> actual behavior regarding text markup: the spec forbids `,`, `'` and
> `"` in the border, yet it seems to work just fine to use them there in
> the current version of Org. I think it's great that Org mode supports
> this, but since the spec hasn't been updated to reflect this change,
> external Org parsers which follow it don't. An example is org-ruby,
> which is used by both GitLab and GitHub to render README files: 
> https://github.com/wallyqs/org-ruby/issues/36

Can you provide an example configuration that we can test for this?

Also, can you send a patch against the documentation if we need to fix
it?  See https://orgmode.org/worg/org-contribute.html



  reply	other threads:[~2020-09-04  9:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-09  8:59 Markup border outdated in spec? kim.lindberger
2020-09-04  9:43 ` Bastien [this message]
2020-09-05 13:19   ` kim.lindberger
2020-09-05 14:07     ` Bastien
  -- strict thread matches above, loose matches on Subject: below --
2020-08-06 12:14 kim.lindberger
2020-08-13  9:15 ` Nicolas Goaziou

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:

  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=87v9gtq3lr.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=kim.lindberger@gmail.com \


* 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


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