Re: [O] org manual not updating when pulling from git

2017-02-08 Thread Achim Gratz
Marco Wahl writes: > Ah! I didn't see target 'compile-dirty'. Thank you for the hint. > > So for now I'm happy with the build process with the existence of > > make compile-dirty > > and further > > make test-dirty > > Also the names are well chosen AFAICT. > > I agree that the commit

Re: [O] org manual not updating when pulling from git

2017-02-08 Thread Marco Wahl
Charles Millar writes: > I use make update. Now it is "working" as before. Good! This indicates that the revert of the commit in question has been applied. This is the commit message: #v+ Revert commit c90c7a33f53ad88dfcc583ad4c77bec306da0b22 targets.mk: Revert

Re: [O] org manual not updating when pulling from git

2017-02-08 Thread Charles Millar
On 02/08/2017 11:39 AM, Nick Dokos wrote: Charles Millar writes: So, how do you update? I forgot about make doc; in the past I used it whenever I had to recompile org from source; after that the pdf "just updated" each time I pulled from git. The question was: *how*

Re: [O] org manual not updating when pulling from git

2017-02-08 Thread Nick Dokos
Charles Millar writes: >> So, how do you update? >> > I forgot about make doc; in the past I used it whenever I had to > recompile org from source; after that the pdf "just updated" each time > I pulled from git. > The question was: *how* do you pull from git? If you use

Re: [O] org manual not updating when pulling from git

2017-02-07 Thread Charles Millar
Hi, On 02/07/2017 02:41 PM, Nick Dokos wrote: Charles Millar writes: When pulling from git, shouldn't the manual be updated if for no other reason than to refelct the most recent org version? It depends on what you mean by "the manual" - the texinfo source is updated,

Re: [O] org manual not updating when pulling from git

2017-02-07 Thread Marco Wahl
Hi! Achim Gratz writes: > Nick Dokos writes: >> "make doc" or "make pdf" will update the PDF file. If you use one of >> the update targets in the makefile, it may have been updating the pdf >> doc under the covers. Taking a look through recent commits, the only one >> that

Re: [O] org manual not updating when pulling from git

2017-02-07 Thread Achim Gratz
Nick Dokos writes: > "make doc" or "make pdf" will update the PDF file. If you use one of > the update targets in the makefile, it may have been updating the pdf > doc under the covers. Taking a look through recent commits, the only one > that might be relevant seems to be this: > > , > |

Re: [O] org manual not updating when pulling from git

2017-02-07 Thread Nick Dokos
Charles Millar writes: > When pulling from git, shouldn't the manual be updated if for no other > reason than to refelct the most recent org version? > It depends on what you mean by "the manual" - the texinfo source is updated, but any derived files (info, pdf) are not:

[O] org manual not updating when pulling from git

2017-02-07 Thread Charles Millar
When pulling from git, shouldn't the manual be updated if for no other reason than to refelct the most recent org version? Up unitl two or three days ago, this was my experience. Now, however, none of the documentation seems to be updating, e g. current Org mode version 9.0.4