emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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 16:43:31 +0200	[thread overview]
Message-ID: <87h8odonl8.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <20180414134754.GA747@smoon.vl-lomov.ru> (Vladimir Lomov's message of "Sat, 14 Apr 2018 21:47:54 +0800")

Vladimir Lomov <lomov.vl@gmail.com> writes:

> Earlier there was "full" "git" version in Manual and I found it convenient
> (I read the manual from time to time to find how to do something in org)
> but now when I open Info with Org manual I'm a bit puzzled, it shows
> version 9.1 while Org from Emacs (I use Emacs from git) shows version
> 9.1.9 and that confuses me completely, which version is "fresh"?

Barring typos and rewording, Org 9.1.9 is expected to have the same
manual as 9.1.0, or 9.1.13. An Org 9.1 manual means it is accurate for
Org 9.1.9. There is nothing puzzling.

> I understand that, but on the other hand, when I/someone uses Org from
> git explicitly it would worth to show the "actual" version in Org Manual
> (as seen by Info). WDYT?

If you use Org from git, you know the manual is on par with HEAD. As
a developer, I don't need to know the "git" version in manual. I'm
curious: what information are you missing?

  reply	other threads:[~2018-04-14 14:43 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 [this message]
2018-04-14 15:31       ` Vladimir Lomov
2018-04-14 15:40         ` 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:
  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=87h8odonl8.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).