Re: [O] [BUG] Org manual without correct org-version
Vladimir Lomov 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 ' 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.
Re: [O] [BUG] Org manual without correct org-version
Hello, ** Nicolas Goaziou [2018-04-14 16:43:31 +0200]: > Vladimir Lomov 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 thought that for software versions 9.1 < 9.1.9 and means that 9.1 preceding the 9.1.9. And first thing that comes to my mind about recent changes is a "template" system, there was '> 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? 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. --- WBR, Vladimir Lomov -- Don't change the reason, just change the excuses! -- Joe Cointment
Re: [O] [BUG] Org manual without correct org-version
Vladimir Lomov 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?
Re: [O] [BUG] Org manual without correct org-version
Hello, ** Nicolas Goaziou [2018-04-13 19:37:09 +0200]: > Hello, > > Vladimir Lomov writes: > >> I'm using org-mode from git and found that now it is not show the >> 'git' version but simply 9.1 in Info file. In doc/ there is >> 'org-version.inc', it is included into 'orgguide.texi' but not in >> 'org.texi'. >> >> As I understand the 'org.texi' is generated from 'org-manual.org', so >> 'org-manual.org' should either somehow includes that file or provide >> other way to get version information. > > Why should it include the exact commit? Manual is for users. I'm not > sure this has any value. 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"? > Actually, "org-manual.org" strips, on purpose, the bugfix number and the > commit release. 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? > Regards, > > -- > Nicolas Goaziou --- WBR, Vladimir Lomov -- After a time, you may find that "having" is not so pleasing a thing, after all, as "wanting." It is not logical, but it is often true. -- Spock, "Amok Time", stardate 3372.7
Re: [O] [BUG] Org manual without correct org-version
Hello, Vladimir Lomov writes: > I'm using org-mode from git and found that now it is not show the > 'git' version but simply 9.1 in Info file. In doc/ there is > 'org-version.inc', it is included into 'orgguide.texi' but not in > 'org.texi'. > > As I understand the 'org.texi' is generated from 'org-manual.org', so > 'org-manual.org' should either somehow includes that file or provide > other way to get version information. Why should it include the exact commit? Manual is for users. I'm not sure this has any value. Actually, "org-manual.org" strips, on purpose, the bugfix number and the commit release. Regards, -- Nicolas Goaziou
[O] [BUG] Org manual without correct org-version
Hello, I'm using org-mode from git and found that now it is not show the 'git' version but simply 9.1 in Info file. In doc/ there is 'org-version.inc', it is included into 'orgguide.texi' but not in 'org.texi'. As I understand the 'org.texi' is generated from 'org-manual.org', so 'org-manual.org' should either somehow includes that file or provide other way to get version information. P.S. I'm practially do the following: 1. git clone/"update" to/the local repo; 2. byte-compile the files; 3. make a package (for my distro). --- WBR, Vladimir Lomov -- Sattinger's Law: It works better if you plug it in.