From: joaotavora@gmail.com (João Távora)
To: guillaume papin <guillaume.papin@epitech.eu>
Cc: "npostavs@users.sourceforge.net" <npostavs@users.sourceforge.net>,
Romanos Skiadas <rom.skiad@gmail.com>,
"lele@metapensiero.it" <lele@metapensiero.it>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>,
"mvoteiza@udel.edu" <mvoteiza@udel.edu>,
"monnier@iro.umontreal.ca" <monnier@iro.umontreal.ca>,
Eli Zaretskii <eliz@gnu.org>,
"sdl.web@gmail.com" <sdl.web@gmail.com>
Subject: Re: New Flymake rewrite in emacs-26
Date: Thu, 12 Oct 2017 14:17:59 +0100 [thread overview]
Message-ID: <87po9s5wu0.fsf@gmail.com> (raw)
In-Reply-To: <HE1PR02MB119575ED3705CCB479B229778D4A0@HE1PR02MB1195.eurprd02.prod.outlook.com> (guillaume papin's message of "Wed, 11 Oct 2017 18:39:31 +0000")
guillaume papin <guillaume.papin@epitech.eu> writes:
> Regarding the way for a project to export it compile options,
> there is somewhat popular, if not standard, method.
> Generate a compilation database[1].
This very interesting and obsviously light years ahead of of my naive
attempt, but apparently requires a non-free external tool.
Though hope I've built my patch around some customization points that
could help you deploy it in a third-party extension.
João
next prev parent reply other threads:[~2017-10-12 13:17 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
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 [this message]
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=87po9s5wu0.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=guillaume.papin@epitech.eu \
--cc=lele@metapensiero.it \
--cc=monnier@iro.umontreal.ca \
--cc=mvoteiza@udel.edu \
--cc=npostavs@users.sourceforge.net \
--cc=rom.skiad@gmail.com \
--cc=sdl.web@gmail.com \
/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).