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>,
Mark Oteiza <mvoteiza@udel.edu>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Eli Zaretskii <eliz@gnu.org>, Leo Liu <sdl.web@gmail.com>
Subject: Re: New Flymake rewrite in emacs-26
Date: Tue, 10 Oct 2017 13:20:33 -0400 [thread overview]
Message-ID: <CAM-tV-_9vV-XBiwwT-mdEmgnA2w=HbBtCJp0OJGwBsr0EWrHjw@mail.gmail.com> (raw)
In-Reply-To: <87y3oj7x60.fsf@gmail.com>
On Tue, Oct 10, 2017 at 1:03 PM, João Távora <joaotavora@gmail.com> wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> Most of the flags we use are for flagging dubious or erroneous code,
>> they should not matter, I think.
>
> I think it’s useful to have Flymake synchronized with these flags, so
> that you are notified visually of these problems ahead of a "real"
> compilation. FWIW this is what the Emacs Lisp backend already does for
> Emacs Lisp sources.
>
>> What compiler flags must be set for Flycheck to work reasonably well
>> with a program's sources? I guess the -I flags, but what else?
>
> For "reasonable" operation, it’s mostly the -I flags, and maybe some
> essential -D flags (In Emacs’s case -Demacs, I think).
>
>> (I have never used Flymake, so my questions are ones of a layman in
I've also hardly ever used flymake, so this may be nonsense, but maybe
you could run 'make --just-print foo.o' to get the exact shell
commands for compiling foo.c. This would bypass any need to know
details of compilation beyond figuring out the target name from the
source.
next prev parent reply other threads:[~2017-10-10 17:20 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAM-tV-_9vV-XBiwwT-mdEmgnA2w=HbBtCJp0OJGwBsr0EWrHjw@mail.gmail.com' \
--to=npostavs@users.sourceforge.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--cc=lele@metapensiero.it \
--cc=monnier@iro.umontreal.ca \
--cc=mvoteiza@udel.edu \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.