From: Nick Dokos <email@example.com>
Subject: Re: Manual on web site is not the latest version
Date: Mon, 17 May 2021 14:34:23 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
William Denton <email@example.com> writes:
> On 28 April 2021, Bastien wrote:
>> Do you still see differences between the doc/org-manual.org and the
>> one published on https://orgmode.org/manual/ ?
>> If so, please point at one or two differences. Thanks!
> Here's a late follow-up. Thanks for checking.
> On the web at https://orgmode.org/manual/Languages.html#Languages
> "Code blocks in the following languages are supported."
> "Additional documentation for some languages is at https://orgmode.org/worg/org-contrib/babel/languages.html."
> In org-manual.org, both sentence are different:
> $ grep -A2 "Code blocks" doc/org-manual.org
> Code blocks in dozens of languages are supported. See Worg for
> specific documentation]].
> William Denton
> Librarian, artist and licensed private investigator.
The online manual is for 9.4 (the released version). What you see in org-manual.org
is for 9.5 (which AFAIK has not been released yet).
"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler
next prev parent reply other threads:[~2021-05-17 19:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 17:31 Manual on web site not showing latest version William Denton
2021-04-23 3:25 ` Manual on web site is not the " William Denton
2021-04-28 5:35 ` Bastien
2021-05-12 17:06 ` William Denton
2021-05-17 18:34 ` Nick Dokos [this message]
2021-05-18 22:39 ` William Denton
2021-05-15 16:47 ` Daniele Nicolodi
2021-08-26 14:00 ` Maxim Nikulin
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 \
* 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).