From: "João Távora" <joaotavora@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: A build problem with flymake.info
Date: Sat, 28 Jul 2018 08:47:36 +0100 [thread overview]
Message-ID: <87y3dv94yv.fsf@gmail.com> (raw)
In-Reply-To: <5B5C19FB.1090700@gmx.at> (martin rudalics's message of "Sat, 28 Jul 2018 09:23:39 +0200")
martin rudalics <rudalics@gmx.at> 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
next prev parent reply other threads:[~2018-07-28 7:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-28 7:23 A build problem with flymake.info martin rudalics
2018-07-28 7:47 ` João Távora [this message]
2018-07-28 8:05 ` Eli Zaretskii
2018-07-28 8:39 ` João Távora
2018-07-28 9:51 ` Eli Zaretskii
2018-07-28 13:27 ` João Távora
2018-07-28 13:48 ` Eli Zaretskii
2018-08-01 8:03 ` João Távora
2018-08-01 9:00 ` Eli Zaretskii
2018-07-28 8:30 ` martin rudalics
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y3dv94yv.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).