On Sun, Aug 25, 2024 at 8:30 PM Christian Brabandt <cbli...@256bit.org> wrote: > > patch 9.1.0696: installing runtime files fails when using SHADOWDIR > > Commit: > https://github.com/vim/vim/commit/663950d700f496c1db09307253e6b1b2a56140d5 > Author: James McCoy <james...@jamessan.com> > Date: Sun Aug 25 20:22:11 2024 +0200 > > patch 9.1.0696: installing runtime files fails when using SHADOWDIR > > Problem: installing runtime files fails when using SHADOWDIR > Solution: revert part of v9.1.0609, since runtime/doc/Makefile's default > value for VIMPROG does not work if vim was built in a SHADOWDIR. > (James McCoy) > > closes: #15575 > > Signed-off-by: James McCoy <james...@jamessan.com> > Signed-off-by: Christian Brabandt <c...@256bit.org> > > diff --git a/src/Makefile b/src/Makefile [...]
Ah, so that's what it was. I had recently noticed that "rm -v runtime/doc/tags" followed by "hg fetch" in the top directory, build in several shadow directories followed by "make install" in one of them didn't rebuild the tags file anymore; I had also found out that "make tags" in the doc subrepo did rebuild it. I said nothing because I thought it might be intentional and I had found a workaround anyway. Today (after this patch) I built in my usual way in my usual 5 shadow dirs followed by "make install" in one of them and "make installvimbin" in the other four (but no separate "make tags"), and checked my $VIMRUNTIME/doc/tags — it was there, and dated "a few seconds ago". Thanks James and Christian ! Best regards, Tony. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAJkCKXuZgv-Q6oWtqbyENV%2BR_UupBkyh%2BOK4q82%2B%2BA8YucYXsw%40mail.gmail.com.
