UseConfigFiles: when verbose, report the reason for skipping a buffer

- Rather than just skipping the buffer, say why it was skipped if
  g:EditorConfig_verbose is truthy.
- Don't print the "Applying EditorConfig" message until we're sure
  we won't be skipping this buffer.

Author: cxw42

plugin/editorconfig.vim

@@ -219,13 +219,16 @@ function! s:UseConfigFiles() abort " Apply config to the current buffer {{{1
         if g:EditorConfig_enable_for_new_buf
             let l:buffer_name = getcwd() . "/."
         else
+            if g:EditorConfig_verbose
+                echo 'Skipping EditorConfig for unnamed buffer'
+            endif
             return
         endif
     endif
 
     if exists("b:EditorConfig_disable") && b:EditorConfig_disable
         if g:EditorConfig_verbose
-            echo 'Skipping EditorConfig for buffer "' . l:buffer_name . '"'
+            echo 'EditorConfig disabled --- skipping buffer "' . l:buffer_name . '"'
         endif
         return
     endif
@@ -249,18 +252,22 @@ function! s:UseConfigFiles() abort " Apply config to the current buffer {{{1
         endif
     endif
 
-    if g:EditorConfig_verbose
-        echo 'Applying EditorConfig ' . s:editorconfig_core_mode .
-            \ ' on file "' . l:buffer_name . '"'
-    endif
-
     " Ignore specific patterns
     for pattern in g:EditorConfig_exclude_patterns
         if l:buffer_name =~ pattern
+            if g:EditorConfig_verbose
+                echo 'Skipping EditorConfig for buffer "' . l:buffer_name .
+                    \ '" based on pattern "' . pattern . '"'
+            endif
             return
         endif
     endfor
 
+    if g:EditorConfig_verbose
+        echo 'Applying EditorConfig ' . s:editorconfig_core_mode .
+            \ ' on file "' . l:buffer_name . '"'
+    endif
+
     if s:editorconfig_core_mode ==? 'vim_core'
         if s:UseConfigFiles_VimCore(l:buffer_name) == 0
             let b:editorconfig_applied = 1