Re: Three Flymake backends Was Re: Two issues with the new Flymake

[Dmitry Gutov]

On 11/5/17 2:59 PM, João Távora wrote:

> Oops. But I've just pushed the correct set emacs-26 if you want to have
> a look now.

Thanks! Now we have a backend for 'ruby -w', that's great, but Rubocop 
has become a pretty essential tool in Ruby world. For our team, at least.

So sooner or later we'll need a backend for it too, for parity with 
Flycheck.

> > > So I'm thinking that, for master (_not_ emacs-26) we could use a
> > > declarative flymake-define-simple-backend macro.
> > Why not make it a function? From what I can see, the usage will just
> > have to quote the first two arguments.
>
> Because the macro defines a new function.

Ah, yes. It would have to use 'eval' in that case.

Although the other option, I think, is for the said function to return a 
lambda. The return value could be used with `defalias' or with 
`add-hook' directly.