From: Noam Postavsky <npostavs@users.sourceforge.net>
To: "João Távora" <joaotavora@gmail.com>
Cc: Lele Gaifax <lele@metapensiero.it>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: New Flymake rewrite in emacs-26
Date: Fri, 6 Oct 2017 09:24:43 -0400 [thread overview]
Message-ID: <CAM-tV-8r7fchc58zWPM3MQMz+XCn5EFpZgvcgwVy-ariwThmTw@mail.gmail.com> (raw)
In-Reply-To: <87vajszaac.fsf@gmail.com>
On Fri, Oct 6, 2017 at 9:16 AM, João Távora <joaotavora@gmail.com> wrote:
> I'm to blame for changing doctyle.texi to ../emacs/docstyle.texi. I
> needed it to fix M-x makeinfo-buffer in the flymake.texi, since there is
> no doc/misc/docstyle.texi.
>
> It sounded a good idea to me at the time, but I forgot to ask here. What
> exactly is an "out-of-tree" build?
In short, when you call ./configure and make from a different
directory than the source's toplevel.
Actually, the official term seems to be "Parallel Build Tree"
https://www.gnu.org/software/automake/manual/html_node/VPATH-Builds.html
Anyway, I don't really understand how the @include texi path works, I
guess the makefile sets it up so that just the basename is enough.
Perhaps there is something similar that could be done via
.dir-locals.el for M-x makeinfo-buffer?
next prev parent reply other threads:[~2017-10-06 13:24 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 14:05 New Flymake rewrite in emacs-26 João Távora
2017-10-03 15:00 ` Eli Zaretskii
2017-10-04 11:58 ` Lele Gaifax
2017-10-04 13:41 ` Lele Gaifax
2017-10-04 16:08 ` João Távora
2017-10-04 16:42 ` Lele Gaifax
2017-10-04 18:11 ` Lele Gaifax
2017-10-05 2:21 ` João Távora
2017-10-05 11:42 ` Lele Gaifax
2017-10-05 23:32 ` Noam Postavsky
2017-10-06 13:16 ` João Távora
2017-10-06 13:24 ` Noam Postavsky [this message]
2017-10-06 15:48 ` João Távora
2017-10-07 7:37 ` Lele Gaifax
2017-10-07 16:08 ` João Távora
2017-10-10 12:25 ` João Távora
2017-10-10 14:18 ` Eli Zaretskii
2017-10-10 15:09 ` João Távora
2017-10-10 15:53 ` Eli Zaretskii
2017-10-10 16:25 ` João Távora
2017-10-10 16:40 ` Eli Zaretskii
2017-10-10 17:03 ` João Távora
2017-10-10 17:20 ` Noam Postavsky
2017-10-11 0:07 ` João Távora
2017-10-11 0:59 ` Noam Postavsky
2017-10-11 10:39 ` Eli Zaretskii
2017-10-11 12:16 ` Noam Postavsky
2017-10-11 12:25 ` João Távora
2017-10-11 10:24 ` Eli Zaretskii
2017-10-11 12:01 ` João Távora
2017-10-11 12:13 ` Eli Zaretskii
2017-10-11 13:41 ` João Távora
2017-10-11 17:49 ` Romanos Skiadas
2017-10-11 18:39 ` guillaume papin
2017-10-12 13:17 ` João Távora
2017-10-11 20:25 ` Stefan Monnier
2017-10-12 13:10 ` João Távora
2017-10-12 13:43 ` Stefan Monnier
2017-10-12 13:56 ` João Távora
2017-10-11 13:11 ` Mark Oteiza
2017-10-10 17:23 ` Eli Zaretskii
2017-10-11 11:11 ` Lele Gaifax
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=CAM-tV-8r7fchc58zWPM3MQMz+XCn5EFpZgvcgwVy-ariwThmTw@mail.gmail.com \
--to=npostavs@users.sourceforge.net \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--cc=lele@metapensiero.it \
/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).