From: "João Távora" <joaotavora@gmail.com>
To: Petko Bordjukov <bordjukov@gmail.com>
Cc: 31760@debbugs.gnu.org, dgutov@yandex.ru
Subject: bug#31760: 26.1; ruby-mode enables flymake-rubocop by default if the rubocop executable exists
Date: Fri, 08 Jun 2018 19:42:21 +0100 [thread overview]
Message-ID: <87po11i0he.fsf@gmail.com> (raw)
In-Reply-To: <87k1r972fp.wl-bordjukov@gmail.com> (Petko Bordjukov's message of "Fri, 08 Jun 2018 17:55:38 +0300")
Petko Bordjukov <bordjukov@gmail.com> writes:
> Emacs 26.1 enables flymake-rubocop by default if the rubocop executable
> is present in the system. Since most if not all of the warnings that
> Rubocop generates are not raised by Ruby I consider them not adopted by
> the Ruby community by default. Based on that, I propose that either
> using Rubocop by default is turned off, or at least a more inteligent
> per-project Rubocop detection scheme is implemented.
>
Paging Dmitry :-)
next prev parent reply other threads:[~2018-06-08 18:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 14:55 bug#31760: 26.1; ruby-mode enables flymake-rubocop by default if the rubocop executable exists Petko Bordjukov
2018-06-08 18:42 ` João Távora [this message]
2018-06-15 15:16 ` Dmitry Gutov
2018-06-15 17:54 ` Bozhidar Batsov
2018-06-16 9:07 ` Petko Bordjukov
2018-06-16 9:31 ` Bozhidar Batsov
2018-06-16 9:36 ` Bozhidar Batsov
2018-06-16 19:47 ` Petko Bordjukov
2018-06-16 19:55 ` Bozhidar Batsov
2018-06-16 15:32 ` João Távora
2018-06-16 19:54 ` Petko Bordjukov
2018-06-18 14:02 ` Dmitry Gutov
2018-06-18 14:09 ` Bozhidar Batsov
2018-12-25 15:36 ` 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=87po11i0he.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=31760@debbugs.gnu.org \
--cc=bordjukov@gmail.com \
--cc=dgutov@yandex.ru \
/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).