From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Vladimir Lomov <lomov.vl@gmail.com>
Cc: General discussions about Org-mode <emacs-orgmode@gnu.org>
Subject: Re: [BUG] Org manual without correct org-version
Date: Sat, 14 Apr 2018 17:40:10 +0200 [thread overview]
Message-ID: <87a7u5okyt.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <20180414153123.GC747@smoon.vl-lomov.ru> (Vladimir Lomov's message of "Sat, 14 Apr 2018 23:31:23 +0800")
Vladimir Lomov <lomov.vl@gmail.com> writes:
> I thought that for software versions 9.1 < 9.1.9 and means that 9.1
> preceding the 9.1.9.
We are not talking about software version but manual version.
> And first thing that comes to my mind about recent
> changes is a "template" system, there was '<s' and etc now it is 'C-c
> C-,'. The '9.1' version (org from git) has 'Structure Templates' while
> '9.1.9' version (org shipped with Emacs) doesn't have that section.
If you use Org from git master's branch (aka development branch), you
should know that it is, for the time being, akin to Org 9.2-alpha.
There, I suggest to use "org-manual.org" instead of Org info manual,
which is bound to be outdated.
If you use Org from maint branch, there is no such problem: the 9.1
manual is accurate.
> I prefer search for information in most recent docs than in "out-dated"
> (see example with 'Structure Templates' above). So simple check of
> version would help to find out what document is 'fresh' enough.
Again, this has nothing to do with manual version. See above.
prev parent reply other threads:[~2018-04-14 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 5:07 [BUG] Org manual without correct org-version Vladimir Lomov
2018-04-13 17:37 ` Nicolas Goaziou
2018-04-14 13:47 ` Vladimir Lomov
2018-04-14 14:43 ` Nicolas Goaziou
2018-04-14 15:31 ` Vladimir Lomov
2018-04-14 15:40 ` Nicolas Goaziou [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=87a7u5okyt.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=lomov.vl@gmail.com \
/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).