Re: A build problem with flymake.info

[João Távora]

martin rudalics <address@hidden> writes:

> With separate build directories making the texi files currently fails as
>
> ../../../doc/misc/flymake.texi:7: @include `../emacs/docstyle.texi': No such 
> file or directory.
> make[2]: *** [../../../doc/misc/../../info/flymake.info] Error 1

Sorry, I broke it again with 15f4cdd873:

      Mention use of C-h . (display-local-help) in Flymake manual
     
      Fixes: Bug#31921

This is something I had previously fixed with 0d0265bf50e190

      Fix @include directive in Flymake doc
     
      * doc/misc/flymake.texi: Don't @include a relative path.

I just pushed a new fix in 77deaf9a1d750

> Second builds usually succeed.  Is there any reason for flymake.texi to
> have and/or hardcode @include ../emacs/docstyle.texi?

I sometimes change the line to `../emacs/docstyle.texi` so I can build
quickly with C-c C-c while editing the file.  Then I forget to take it out.  I

I wish Texinfo mode had some load path variable or something exposed to
elisp that I could use to avoid this bug and still benefit from snappy
C-c C-c's.  Or some other local-variable or dir-variable based
mechanism...

João