From 2ef9f8fc2ec4b81394bec1f82e068ca93f57ad0a Mon Sep 17 00:00:00 2001
From: Marco Hinz <mh.codebro@gmail.com>
Date: Fri, 8 Jul 2016 21:28:03 +0200
Subject: [PATCH] Debug: move up Verbosity section

---
 README.md | 86 +++++++++++++++++++++++++++----------------------------
 1 file changed, 43 insertions(+), 43 deletions(-)

diff --git a/README.md b/README.md
index 631d460..27d02f5 100644
--- a/README.md
+++ b/README.md
@@ -85,9 +85,9 @@ My [vimrc](https://github.com/mhinz/dotfiles/blob/master/vim/vimrc).
 #### [Debugging](#debugging-1)
 
 - [General tips](#general-tips)
+- [Verbosity](#verbosity)
 - [Profiling startup time](#profiling-startup-time)
 - [Profiling at runtime](#profiling-at-runtime)
-- [Verbosity](#verbosity)
 - [Debugging Vim scripts](#debugging-vim-scripts)
 - [Debugging syntax files](#debugging-syntax-files)
 
@@ -2103,6 +2103,48 @@ the active upper half. Move the `:finish` to the middle of _that_ half.
 Otherwise, the issue is in the inactive lower half. Move the `:finish` to the
 middle of _that_ half. And so on.
 
+#### Verbosity
+
+Another useful way for observing what Vim is currently doing is increasing the
+verbosity level. Currently Vim supports 9 different levels. See `:h 'verbose'`
+for the full list.
+
+```vim
+:e /tmp/foo
+:set verbose=2
+:w
+:set verbose=0
+```
+
+This would show all the files that get sourced, e.g. the undo file or various
+plugins that act on saving.
+
+If you only want increase verbosity for a single command, there's also
+`:verbose`, which simply gets put in front of any other command. It takes the
+verbosity level as count and defaults to 1:
+
+```vim
+:verb set verbose
+"  verbose=1
+:10verb set verbose
+"  verbose=10
+```
+
+It's very often used with its default verbosity level 1 to show where an option
+was set last:
+
+```vim
+:verb set ai?
+"      Last set from ~/.vim/vimrc
+```
+
+Naturally, the higher the verbosity level the more overwhelming the output. But
+fear no more, you can simply redirect the output to a file:
+
+```vim
+:set verbosefile=/tmp/foo | 15verbose echo "foo" | vsplit /tmp/foo
+```
+
 #### Profiling startup time
 
 Vim startup feels slow? Time to crunch some numbers:
@@ -2147,48 +2189,6 @@ two different sections `FUNCTIONS SORTED ON TOTAL TIME` and `FUNCTIONS SORTED ON
 SELF TIME` that are worth gold. At a quick glance you can see, if a certain
 function is taking too long.
 
-#### Verbosity
-
-Another useful way for observing what Vim is currently doing is increasing the
-verbosity level. Currently Vim supports 9 different levels. See `:h 'verbose'`
-for the full list.
-
-```vim
-:e /tmp/foo
-:set verbose=2
-:w
-:set verbose=0
-```
-
-This would show all the files that get sourced, e.g. the undo file or various
-plugins that act on saving.
-
-If you only want increase verbosity for a single command, there's also
-`:verbose`, which simply gets put in front of any other command. It takes the
-verbosity level as count and defaults to 1:
-
-```vim
-:verb set verbose
-"  verbose=1
-:10verb set verbose
-"  verbose=10
-```
-
-It's very often used with its default verbosity level 1 to show where an option
-was set last:
-
-```vim
-:verb set ai?
-"      Last set from ~/.vim/vimrc
-```
-
-Naturally, the higher the verbosity level the more overwhelming the output. But
-fear no more, you can simply redirect the output to a file:
-
-```vim
-:set verbosefile=/tmp/foo | 15verbose echo "foo" | vsplit /tmp/foo
-```
-
 #### Debugging Vim scripts
 
 If you ever used a command-line debugger before, `:debug` will quickly feel