unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: "João Távora" <joaotavora@gmail.com>
Cc: Mark Oteiza <mvoteiza@udel.edu>,
	Lele Gaifax <lele@metapensiero.it>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-devel@gnu.org
Subject: Re: Three Flymake backends Was Re: Two issues with the new Flymake
Date: Sun, 5 Nov 2017 15:04:49 +0200	[thread overview]
Message-ID: <04d1a3b5-9651-c46d-0e3b-7e1c858cda02@yandex.ru> (raw)
In-Reply-To: <87a800swy5.fsf@gmail.com>

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.



  reply	other threads:[~2017-11-05 13:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-03  9:50 Two issues with the new Flymake Lele Gaifax
2017-11-03 12:33 ` Stefan Monnier
2017-11-03 14:07   ` Lele Gaifax
2017-11-03 16:59     ` João Távora
2017-11-03 17:15       ` Stefan Monnier
2017-11-03 20:17 ` Three Flymake backends Was " João Távora
2017-11-04 15:30   ` Stefan Monnier
2017-11-04 23:17     ` João Távora
2017-11-05 12:50   ` Dmitry Gutov
2017-11-05 12:59     ` João Távora
2017-11-05 13:04       ` Dmitry Gutov [this message]
2017-11-05 13:22         ` João Távora
2017-11-05 20:14           ` Dmitry Gutov
2017-11-05 21:05             ` João Távora
2017-11-05 23:56               ` Dmitry Gutov
2017-11-06  9:48                 ` João Távora
2017-11-06 10:35                   ` Dmitry Gutov
2017-11-06 11:08                     ` João Távora
2017-11-13  0:23                       ` Dmitry Gutov

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=04d1a3b5-9651-c46d-0e3b-7e1c858cda02@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=lele@metapensiero.it \
    --cc=monnier@iro.umontreal.ca \
    --cc=mvoteiza@udel.edu \
    /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).