Re: New Flymake rewrite in emacs-26

[Noam Postavsky <npostavs@users.sourceforge.net>]

On Tue, Oct 10, 2017 at 8:07 PM, João Távora <joaotavora@gmail.com> wrote:

> Unfortunately, not all flags make sense for flymake, like the -M family
> of flags.

Oh, huh. I hadn't thought of that. Do the -M flags do any harm though?

> Ideally, i’d need a way to parse this big string of flags back
> into, say, an alist, and cherry pick the -I, -D, and -W flags from that
> set. But I’m afraid split-string will insufficiently deal with escaped
> spaces in the output.

There was some talk of extracting the eshell code into a separate
function that could provide "real" shell parsing. The downside of this
approach is that it would take some work (eshell code is generally
kind of hairy), and it will probably never be 100% since the actual
Makefile isn't using eshell to parse.

Another possibility is to put an echoing command in front and exploit
the shell's parsing directly, e.g.,

  printf '%s\0' gcc -c -Demacs -I. -I. -I../lib -I../ ...

should give you some output that you can split-string on NUL without
worry. Instead of printf, which may not be available, you could use
emacs.