[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] Flymake support for C/C++

From: Sami Kerola
Subject: Re: [PATCH] Flymake support for C/C++
Date: Sat, 14 Oct 2017 08:58:58 +0100

On 14 October 2017 at 08:10, Reuben Thomas <address@hidden> wrote:
> On 14 October 2017 at 02:34, Richard Stallman <address@hidden> wrote:
>> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
>> [[[ whether defending the US Constitution against all enemies,     ]]]
>> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>>   > *: Sadly, GNU Hello no longer works since it uses a backquoted shell
>>   >   expression that the current implementation can't intercept (my old
>>   >   use-emacs-as-a-shell-parser )
>> It is important to fix this, since it is not good for Flymake to fail
>> on the GNU example of proper packaging.
>> It could be fixed in Flymake or fixed in GNU Hello.
>> Which one is better?
> These days, it seems much better to use Flycheck than Flymake (that's
> certainly what I do). See https://github.com/flycheck/flycheck
> It would be a pity for Flymake to become yet another part of Emacs that
> developers spend time updating and users largely ignore; better to spin it
> off into ELPA, and if people still want to work on it there, fine.
> Meanwhile, why not use Flycheck by default (in the same way as we've
> "in-sourced" Org and other packages)?

I tried to reproduce following comple output[1] without luck[2].

gcc -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I. -I.. -I.
-I. -I.. -I../intl -I../intl    -g -O2 -c `test -f 'hello.c' || echo

Perhaps backticks are coming from autotools. Mine are:

autoconf (GNU Autoconf) 2.69
automake (GNU automake) 1.15.1

[1] as mentioned in earlier in thread:

[2] tested using hello-2.10 distribution package, and latest upstream
version 4d0301f23b1666cf466a0ac281a0ea008abe70bb.

Sami Kerola

reply via email to

[Prev in Thread] Current Thread [Next in Thread]