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: Sat, 05 Sep 2020 16:07:44 +0200	[thread overview]
Message-ID: <87o8mkgvv3.fsf@gnu.org> (raw)
In-Reply-To: <a6d7a26f06653f0a1837f490de85a32608fa774b.camel@gmail.com> (kim lindberger's message of "Sat, 05 Sep 2020 15:19:06 +0200")

Hi Kim,

kim.lindberger@gmail.com writes:

> I believe Nicolas Goaziou fixed this in the spec already. 

I should have thought of this :)  Thanks for confirming!

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

Thanks for this additional information, always useful for the
casual reader of the list (hello casual reader!)


  reply	other threads:[~2020-09-05 14:08 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
2020-09-05 14:07     ` Bastien [this message]
  -- 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=87o8mkgvv3.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).