From: Dmitry Gutov <dgutov@yandex.ru>
To: Ergus <spacibba@aol.com>
Cc: Glenn Morris <rgm@gnu.org>, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master bc780a4: * test/lisp/progmodes/flymake-tests.el (ruby-backend): Skip on hydra.
Date: Wed, 26 Jun 2019 19:21:19 +0300 [thread overview]
Message-ID: <a5bba2cc-50fa-86dd-11e5-cd817a96253e@yandex.ru> (raw)
In-Reply-To: <20190626160452.lalvf6xza6rrxm2z@Ergus>
On 26.06.2019 19:04, Ergus wrote:
> Hi Sorry if this is not really related 100%.
It's 100% unrelated.
> And I see no errors detected. I tried many things and
> flymake-running-backends prints.
First of all, you just look at the value of flymake-diagnostic-functions.
Apparently, c++-mode uses flymake-cc.
You might want to go ahead and read it, but it's a minimalistic solution
that relies on Make and a particular target being present (see
flymake-cc-use-special-make-target). Would I be correct in assuming that
you don't have it?
Flycheck probably has more sophisticated checkers, but the new Flymake
API is not too hard. You should be able to port whatever checker you
have been using to Flymake without too much difficulty.
next prev parent reply other threads:[~2019-06-26 16:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190625202332.25129.77823@vcs0.savannah.gnu.org>
[not found] ` <20190625202333.7934B20990@vcs0.savannah.gnu.org>
2019-06-26 13:54 ` [Emacs-diffs] master bc780a4: * test/lisp/progmodes/flymake-tests.el (ruby-backend): Skip on hydra Dmitry Gutov
2019-06-26 16:04 ` Ergus
2019-06-26 16:21 ` Dmitry Gutov [this message]
2019-06-26 16:23 ` Ergus
2019-06-26 16:27 ` Dmitry Gutov
2019-06-26 17:23 ` Ergus
2019-06-26 19:20 ` Dmitry Gutov
2019-06-29 2:11 ` Glenn Morris
2019-07-03 13:57 ` Dmitry Gutov
2019-07-06 22:57 ` João Távora
2019-07-07 22:16 ` Dmitry Gutov
2019-07-14 1:53 ` Glenn Morris
2019-07-30 14:00 ` Dmitry Gutov
2019-08-15 17:11 ` Glenn Morris
2019-09-28 8:22 ` Dmitry Gutov
2019-09-28 9:15 ` Michael Albinus
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=a5bba2cc-50fa-86dd-11e5-cd817a96253e@yandex.ru \
--to=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.org \
--cc=spacibba@aol.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.