Re: Re: [PATCH] Re: html-export mangels mailto: links

[Nick Dokos <nicholas.dokos@hp.com>]

Achim Gratz <Stromeko@nexgo.de> wrote:

> Eric S Fraga <ucecesf@ucl.ac.uk> writes:
> > it's the output of "M-x org-version RET" as opposed to the value of
> > org-version.
> 
> They both deliver the same result "7.01trans" for me, that's why I'm
> asking...
> 

org-version makes some assumptions: it calculates a directory as follows

   (concat (file-name-directory (locate-library "org")) "../" ))

and then looks for a ``.git'' subdirectory in that directory. If it is
found, then all is good: it does a ``git describe'' variation to get the
release part.  But if it is not found, then it falls back to the bare
version (without the release part).

E.g. if you git pull into one place and then install the .el files
somewhere else, the .git subdirectory will not be found.

So evaluate these two expressions:

(setq dir (concat (file-name-directory (locate-library "org")) "../" )))
(file-exists-p (expand-file-name ".git" dir))

and you'll probably find that the second one returns nil in your case.

One way to get the release part: arrange your load-path to load org.el[c]
(and the other org .el or .elc files) from the lisp subdirectory of your
git repository.

HTH,
Nick