-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prevent ALE from linting diffs #2399
Comments
Do you know if there's some way to detect if a Vim buffer is a buffer being used for displaying diffs with common plugins? |
Not that I can see, but I'm still looking into it. |
gina.vim uses &diff https://github.com/lambdalisue/gina.vim/blob/master/autoload/gina/util.vim#L233 fugitive seems to do the same |
as an extra for gina, it also uses file protocols |
I have an autocommand in my vimrc to at least not open up the loclist for a diff. It's probably not a perfect solution, but it might give you an idea of what to do.
|
|
…aying diffs" This reverts commit 9a0ece1.
…aying diffs" This reverts commit 9a0ece1.
…aying diffs" This reverts commit 9a0ece1.
…aying diffs" This reverts commit 9a0ece1.
…aying diffs" This reverts commit 9a0ece1.
I use Vim as my diff and merge tool for Git. When running
Gdiff
in a file in Vim, I get the split window with diffs displayed with no issues (linting). When I run thedifftool
alias for Git from the command line, it opens up a similar split, but this time index version of the file is pulling from a temp directory/private/vars/folder
and ALE lints the file. It seems that because this file is outside of the repo it doesn't use the rubocop config and seems to pull from a default set of rules.Ideally, ALE wouldn't lint files when viewed via vimdiff or Gdiff.
The text was updated successfully, but these errors were encountered: