emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Cc: Leo Butler <Leo.Butler@umanitoba.ca>
Subject: Re: render math in README.org on github
Date: Sat, 21 Dec 2024 19:53:32 +0700	[thread overview]
Message-ID: <db465f9d-b0ef-4098-93e3-41b286ff4222@gmail.com> (raw)
In-Reply-To: <87wmfu6vcs.fsf@t14.reltub.ca>

On 21/12/2024 01:51, Leo Butler wrote:
> On Fri, Dec 20 2024, Nikolaos Chatzikonstantinou wrote:
> 
>> Do you want mathjax when viewing the readme file?
> 
> Yes. The only documentation I have seen refers to markdown.
> 
> On a hunch, I changed all the math delimiters in my README.org to $ and
> $$ and that worked. But, I would prefer to use the math delimiters \(\)
> and \[\] and have that work.

I suggest to be realistic and to adjust your expectations. There have 
been no commits to <https://github.com/wallyqs/org-ruby> last years and 
GitHub does not use the latest release.

Use a kind of Pidgin Org that is compatible with both org-ruby and 
Emacs. If GitHub renders $...$ and $$...$$ then use it, despite they are 
going to be deprecated in Org.

<https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions>
<https://github.blog/news-insights/product-news/math-support-in-markdown/>

You may try to file a bug against <https://github.com/github/markup/> or 
some other project that really contains MathJax config to extend the 
list of supported math delimiters for Org files.

>> If github is broken it is on their end, they don't have the best
>> coverage of org features.

GitHub and GitLab just use org-ruby gem, they do not develop it.

org-ruby is more close to regexps used for fontlock than to 
org-element.el parser used for export. There are a lot of Org features 
that are not recognized by org-ruby. In particular, org-ruby is unaware 
of math (TeX) at all, it is just semi-transparent for this kind of 
constructs.

And finally, GitHub performs security audit before update of deployed 
gem version. Likely they will be reluctant to do it frequently pulling 
changes from a fork.

>> On Fri, Dec 20, 2024, 12:26 PM Leo Butler wrote:
>>
>>> The best that I could find was a bug report by karthink [fn:1] that
>>> refers to following instructions on a wiki. But, I can't find that wiki
[...]
>>> [fn:1] https://github.com/gollum/gollum/issues/1588

See the description of the project and its wiki. As to specific 
superscript issues, add

#+options: ^:nil

as a workaround.


      reply	other threads:[~2024-12-21 13:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20 17:20 render math in README.org on github Leo Butler
2024-12-20 18:10 ` Nikolaos Chatzikonstantinou
2024-12-20 18:51   ` Leo Butler
2024-12-21 12:53     ` Max Nikulin [this message]

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=db465f9d-b0ef-4098-93e3-41b286ff4222@gmail.com \
    --to=manikulin@gmail.com \
    --cc=Leo.Butler@umanitoba.ca \
    --cc=emacs-orgmode@gnu.org \
    /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).