emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: kim.lindberger@gmail.com
To: Bastien <bzg@gnu.org>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Markup border outdated in spec?
Date: Sat, 05 Sep 2020 15:19:06 +0200	[thread overview]
Message-ID: <a6d7a26f06653f0a1837f490de85a32608fa774b.camel@gmail.com> (raw)
In-Reply-To: <87v9gtq3lr.fsf@gnu.org>

Hi Bastien!

I believe Nicolas Goaziou fixed this in the spec already. I sent this
in two times because my first message got stuck, but eventually both
were sent to the list; I'm sorry for the confusion.

The use-case where I ran into this issue, if you're curious, is the
README.org file here https://github.com/talyz/fromElisp. As you can
see, some of the function names under the `Other functions` are
rendered incorrectly by the GitHub renderer, but renders and exports
just fine in Org.

Best regards,

On Fri, 2020-09-04 at 11:43 +0200, Bastien wrote:
> 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
> Thanks!

  reply	other threads:[~2020-09-05 13:32 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
2020-09-05 13:19   ` kim.lindberger [this message]
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=a6d7a26f06653f0a1837f490de85a32608fa774b.camel@gmail.com \
    --to=kim.lindberger@gmail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \


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