From: Dmitry Gutov <dgutov@yandex.ru>
To: Bozhidar Batsov <bozhidar@batsov.com>
Cc: "Petko Bordjukov" <bordjukov@gmail.com>,
"João Távora" <joaotavora@gmail.com>,
31760-done@debbugs.gnu.org
Subject: bug#31760: 26.1; ruby-mode enables flymake-rubocop by default if the rubocop executable exists
Date: Tue, 25 Dec 2018 17:36:34 +0200 [thread overview]
Message-ID: <1b89e59f-369b-86e1-2d5b-6daab8ac82f9@yandex.ru> (raw)
In-Reply-To: <CAM9Zgm0_Lv_xDG__-13TENHsR+CbYuBUK8qAhZ-RAyQxsZh3Gw@mail.gmail.com>
Version: 27.1
On 18.06.2018 17:09, Bozhidar Batsov wrote:
> I guess you can just look for .rubocop.yml in the root of the project.
> That's not a precise way to infer if someone wants to use RuboCop, but
> it should be good enough for most people (relatively few people have
> global RuboCop configs).
>
> I wonder if it won't be good to have a lint-mode only option as well -
> generally `rubocop --lint` will show only things that are important to
> fix, but it's much nicer than `ruby -w`. So, I'd still use rubocop for
> linting if RuboCop is installed and use it for everything else only when
> the project has some project config.
Thanks, Bozhidar!
I've tried this approach, and it works well. So as of commit
a361cc88a15e9c39f17145f9acd1ea4a8ca70461, we call rubocop with --lint if
there's no .rubocop.yml in any parent directory of the current file.
It was an easy tweak.
prev parent reply other threads:[~2018-12-25 15:36 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
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 [this message]
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=1b89e59f-369b-86e1-2d5b-6daab8ac82f9@yandex.ru \
--to=dgutov@yandex.ru \
--cc=31760-done@debbugs.gnu.org \
--cc=bordjukov@gmail.com \
--cc=bozhidar@batsov.com \
--cc=joaotavora@gmail.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.