PageRenderTime 62ms CodeModel.GetById 26ms RepoModel.GetById 0ms app.codeStats 0ms

/pack/bundle/opt/ferret/README.md

https://bitbucket.org/skeept/dotvim
Markdown | 857 lines | 478 code | 379 blank | 0 comment | 0 complexity | dc41a680e77dc6921ae7512fcc8370cb MD5 | raw file
Possible License(s): GPL-3.0, WTFPL, BSD-3-Clause, CC-BY-SA-4.0, AGPL-3.0, LGPL-3.0, BSD-2-Clause, MIT, AGPL-1.0

Large files files are truncated, but you can click here to view the full file

    

  1. <p align="center">
    2. 

  2.   <img src="https://raw.githubusercontent.com/wincent/ferret/media/ferret.jpg" />
    3. 

  3. </p>
    4. 

  4. <p align="center">
    5. 

  5.   <img src="https://raw.githubusercontent.com/wincent/ferret/media/ferret.gif" />
    6. 

  6. </p>
    7. 

  7. 

  8. # ferret<a name="ferret-ferret" href="#user-content-ferret-ferret"></a>
    9. 

  9. 

  10. 

  11. ## Intro<a name="ferret-intro" href="#user-content-ferret-intro"></a>
    12. 

  12. 

  13. > &quot;ferret (verb)<br />(ferret something out) search tenaciously for and find something: she had the ability to ferret out the facts.&quot;
    14. 

  14. 

  15. <p align="right"><a name="ferret-features" href="#user-content-ferret-features"><code>ferret-features</code></a></p>
    16. 

  16. Ferret improves Vim's multi-file search in four ways:
    17. 

    18. 

  18. 

  19. ### 1. Powerful multi-file search<a name="ferret-1-powerful-multi-file-search" href="#user-content-ferret-1-powerful-multi-file-search"></a>
    20. 

  20. 

  21. Ferret provides an <strong>[`:Ack`](#user-content-ack)</strong> command for searching across multiple files using ripgrep (https://github.com/BurntSushi/ripgrep), The Silver Searcher (https://github.com/ggreer/the_silver_searcher), or Ack (http://beyondgrep.com/). Support for passing options through to the underlying search command exists, along with the ability to use full regular expression syntax without doing special escaping. On modern versions of Vim (version 8 or higher, or Neovim), searches are performed asynchronously (without blocking the UI).
    22. 

  22. 

  23. Shortcut mappings are provided to start an <strong>[`:Ack`](#user-content-ack)</strong> search (&lt;leader&gt;a) or to search for the word currently under the cursor (&lt;leader&gt;s).
    24. 

  24. 

  25. Results are normally displayed in the <strong>`quickfix`</strong> window, but Ferret also provides a <strong>[`:Lack`](#user-content-lack)</strong> command that behaves like <strong>[`:Ack`](#user-content-ack)</strong> but uses the <strong>`location-list`</strong> instead, and a &lt;leader&gt;l mapping as a shortcut to <strong>[`:Lack`](#user-content-lack)</strong>.
    26. 

  26. 

  27. <strong>[`:Back`](#user-content-back)</strong> and <strong>[`:Black`](#user-content-black)</strong> are analogous to <strong>[`:Ack`](#user-content-ack)</strong> and <strong>[`:Lack`](#user-content-lack)</strong>, but scoped to search within currently open buffers only. <strong>[`:Quack`](#user-content-quack)</strong> is scoped to search among the files currently in the <strong>`quickfix`</strong> list.
    28. 

  28. 

  29. 

  30. ### 2. Streamlined multi-file replace<a name="ferret-2-streamlined-multi-file-replace" href="#user-content-ferret-2-streamlined-multi-file-replace"></a>
    31. 

  31. 

  32. The companion to <strong>[`:Ack`](#user-content-ack)</strong> is <strong>[`:Acks`](#user-content-acks)</strong> (mnemonic: &quot;Ack substitute&quot;, accessible via shortcut &lt;leader&gt;r), which allows you to run a multi-file replace across all the files placed in the <strong>`quickfix`</strong> window by a previous invocation of <strong>[`:Ack`](#user-content-ack)</strong> (or <strong>[`:Back`](#user-content-back)</strong>, or <strong>[`:Quack`](#user-content-quack)</strong>).
    33. 

  33. 

  34. Correspondingly, results obtained by <strong>[`:Lack`](#user-content-lack)</strong> can be targeted for replacement with <strong>[`:Lacks`](#user-content-lacks)</strong>.
    35. 

  35. 

  36. 

  37. ### 3. Quickfix listing enhancements<a name="ferret-3-quickfix-listing-enhancements" href="#user-content-ferret-3-quickfix-listing-enhancements"></a>
    38. 

  38. 

  39. The <strong>`quickfix`</strong> listing itself is enhanced with settings to improve its usability, and natural mappings that allow quick removal of items from the list (for example, you can reduce clutter in the listing by removing lines that you don't intend to make changes to).
    40. 

    41. 

  41. Additionally, Vim's <strong>`:cn`</strong>, <strong>`:cp`</strong>, <strong>`:cnf`</strong> and <strong>`:cpf`</strong> commands are tweaked to make it easier to immediately identify matches by centering them within the viewport.
    42. 

    43. 

  43. 

  44. ### 4. Easy operations on files in the quickfix listing<a name="ferret-4-easy-operations-on-files-in-the-quickfix-listing" href="#user-content-ferret-4-easy-operations-on-files-in-the-quickfix-listing"></a>
    45. 

  45. 

  46. Finally, Ferret provides a <strong>[`:Qargs`](#user-content-qargs)</strong> command that puts the files currently in the <strong>`quickfix`</strong> listing into the <strong>`:args`</strong> list, where they can be operated on in bulk via the <strong>`:argdo`</strong> command. This is what's used under the covers on older versions of Vim by <strong>[`:Acks`](#user-content-acks)</strong> to do its work (on newer versions the built-in <strong>`:cdo`</strong> or <strong>`:cfdo`</strong> are used instead).
    47. 

    48. 

  48. Ferret also provides a <strong>[`:Largs`](#user-content-largs)</strong> command, which is a <strong>`location-list`</strong> analog for <strong>[`:Qargs`](#user-content-qargs)</strong>.
    49. 

  49. 

  50. 

  51. ## Installation<a name="ferret-installation" href="#user-content-ferret-installation"></a>
    52. 

  52. 

  53. To install Ferret, use your plug-in management system of choice.
    54. 

  54. 

  55. If you don't have a &quot;plug-in management system of choice&quot;, I recommend Pathogen (https://github.com/tpope/vim-pathogen) due to its simplicity and robustness. Assuming that you have Pathogen installed and configured, and that you want to install Ferret into `~/.vim/bundle`, you can do so with:
    56. 

    57. 

  57. ```
    58. 

  58. git clone https://github.com/wincent/ferret.git ~/.vim/bundle/ferret
    59. 

  59. ```
    60. 

  60. 

  61. Alternatively, if you use a Git submodule for each Vim plug-in, you could do the following after `cd`-ing into the top-level of your Git superproject:
    62. 

  62. 

  63. ```
    64. 

  64. git submodule add https://github.com/wincent/ferret.git ~/vim/bundle/ferret
    65. 

  65. git submodule init
    66. 

  66. ```
    67. 

  67. 

  68. To generate help tags under Pathogen, you can do so from inside Vim with:
    69. 

  69. 

  70. ```
    71. 

  71. :call pathogen#helptags()
    72. 

  72. ```
    73. 

  73. 

  74. 

  75. ## Commands<a name="ferret-commands" href="#user-content-ferret-commands"></a>
    76. 

  76. 

  77. <p align="right"><a name="ack" href="#user-content-ack"><code>:Ack</code></a></p>
    78. 

  78. 

  79. ### `:Ack {pattern} {options}`<a name="ferret-ack-pattern-options" href="#user-content-ferret-ack-pattern-options"></a>
    80. 

  80. 

  81. Searches for {pattern} in all the files under the current directory (see <strong>`:pwd`</strong>), unless otherwise overridden via {options}, and displays the results in the <strong>`quickfix`</strong> listing.
    82. 

  82. 

  83. `rg` (ripgrep) then `ag` (The Silver Searcher) will be used preferentially if present on the system, because they are faster, falling back to `ack`/`ack-grep` as needed.
    84. 

  84. 

  85. On newer versions of Vim (version 8 and above), the search process runs asynchronously in the background and does not block the UI.
    86. 

  86. 

  87. Asynchronous searches are preferred because they do not block, despite the fact that Vim itself is single threaded.
    88. 

  88. 

  89. The {pattern} is passed through as-is to the underlying search program, and no escaping is required other than preceding spaces by a single backslash. For example, to search for &quot;\bfoo[0-9]{2} bar\b&quot; (ie. using `ag`'s Perl-style regular expression syntax), you could do:
    90. 

    91. 

  91. ```
    92. 

  92. :Ack \bfoo[0-9]{2}\ bar\b
    93. 

  93. ```
    94. 

  94. 

  95. Likewise, {options} are passed through. In this example, we pass the `-w` option (to search on word boundaries), and scope the search to the &quot;foo&quot; and &quot;bar&quot; subdirectories:
    96. 

  96. 

  97. ```
    98. 

  98. :Ack -w something foo bar
    99. 

  99. ```
    100. 

  100. 

  101. As a convenience &lt;leader&gt;a is set-up (<strong>[`<Plug>(FerretAck)`](#user-content-plugferretack)</strong>) as a shortcut to enter <strong>`Cmdline-mode`</strong> with `:Ack` inserted on the <strong>`Cmdline`</strong>. Likewise &lt;leader&gt;s (<strong>[`<Plug>(FerretAckWord)`](#user-content-plugferretackword)</strong>) is a shortcut for running <strong>[`:Ack`](#user-content-ack)</strong> with the word currently under the cursor.
    102. 

  102. 

  103. <p align="right"><a name="ack" href="#user-content-ack"><code>:Ack!</code></a></p>
    104. 

  104. 

  105. ### `:Ack! {pattern} {options}`<a name="ferret-ack-pattern-options" href="#user-content-ferret-ack-pattern-options"></a>
    106. 

  106. 

  107. Like <strong>[`:Ack`](#user-content-ack)</strong>, but returns all results irrespective of the value of <strong>[`g:FerretMaxResults`](#user-content-gferretmaxresults)</strong>.
    108. 

  108. 

  109. <p align="right"><a name="lack" href="#user-content-lack"><code>:Lack</code></a></p>
    110. 

  110. 

  111. ### `:Lack {pattern} {options}`<a name="ferret-lack-pattern-options" href="#user-content-ferret-lack-pattern-options"></a>
    112. 

  112. 

  113. Just like <strong>[`:Ack`](#user-content-ack)</strong>, but instead of using the <strong>`quickfix`</strong> listing, which is global across an entire Vim instance, it uses the <strong>`location-list`</strong>, which is a per-window construct.
    114. 

  114. 

  115. Note that <strong>[`:Lack`](#user-content-lack)</strong> always runs synchronously via <strong>`:cexpr`</strong>.
    116. 

  116. 

  117. <p align="right"><a name="lack" href="#user-content-lack"><code>:Lack!</code></a></p>
    118. 

  118. 

  119. ### `:Lack! {pattern} {options}`<a name="ferret-lack-pattern-options" href="#user-content-ferret-lack-pattern-options"></a>
    120. 

  120. 

  121. Like <strong>[`:Lack`](#user-content-lack)</strong>, but returns all results irrespective of the value of <strong>[`g:FerretMaxResults`](#user-content-gferretmaxresults)</strong>.
    122. 

  122. 

  123. <p align="right"><a name="back" href="#user-content-back"><code>:Back</code></a></p>
    124. 

  124. 

  125. ### `:Back {pattern} {options}`<a name="ferret-back-pattern-options" href="#user-content-ferret-back-pattern-options"></a>
    126. 

  126. 

  127. Like <strong>[`:Ack`](#user-content-ack)</strong>, but searches only listed buffers. Note that the search is still delegated to the underlying <strong>`'grepprg'`</strong> (`rg`, `ag`, `ack` or `ack-grep`), which means that only buffers written to disk will be searched. If no buffers are written to disk, then <strong>[`:Back`](#user-content-back)</strong> behaves exactly like <strong>[`:Ack`](#user-content-ack)</strong> and will search all files in the current directory.
    128. 

  128. 

  129. <p align="right"><a name="back" href="#user-content-back"><code>:Back!</code></a></p>
    130. 

  130. 

  131. ### `:Back! {pattern} {options}`<a name="ferret-back-pattern-options" href="#user-content-ferret-back-pattern-options"></a>
    132. 

  132. 

  133. Like <strong>[`:Back`](#user-content-back)</strong>, but returns all results irrespective of the value of <strong>[`g:FerretMaxResults`](#user-content-gferretmaxresults)</strong>.
    134. 

  134. 

  135. <p align="right"><a name="black" href="#user-content-black"><code>:Black</code></a></p>
    136. 

  136. 

  137. ### `:Black {pattern} {options}`<a name="ferret-black-pattern-options" href="#user-content-ferret-black-pattern-options"></a>
    138. 

  138. 

  139. Like <strong>[`:Lack`](#user-content-lack)</strong>, but searches only listed buffers. As with <strong>[`:Back`](#user-content-back)</strong>, the search is still delegated to the underlying <strong>`'grepprg'`</strong> (`rg`, `ag`, `ack` or `ack-grep`), which means that only buffers written to disk will be searched. Likewise, If no buffers are written to disk, then <strong>[`:Black`](#user-content-black)</strong> behaves exactly like <strong>[`:Lack`](#user-content-lack)</strong> and will search all files in the current directory.
    140. 

  140. 

  141. <p align="right"><a name="black" href="#user-content-black"><code>:Black!</code></a></p>
    142. 

  142. 

  143. ### `:Black! {pattern} {options}`<a name="ferret-black-pattern-options" href="#user-content-ferret-black-pattern-options"></a>
    144. 

  144. 

  145. Like <strong>[`:Black`](#user-content-black)</strong>, but returns all results irrespective of the value of <strong>[`g:FerretMaxResults`](#user-content-gferretmaxresults)</strong>.
    146. 

  146. 

  147. <p align="right"><a name="quack" href="#user-content-quack"><code>:Quack</code></a></p>
    148. 

  148. 

  149. ### `:Quack {pattern} {options}`<a name="ferret-quack-pattern-options" href="#user-content-ferret-quack-pattern-options"></a>
    150. 

  150. 

  151. Like <strong>[`:Ack`](#user-content-ack)</strong>, but searches only among files currently in the <strong>`quickfix`</strong> listing. Note that the search is still delegated to the underlying <strong>`'grepprg'`</strong> (`rg`, `ag`, `ack` or `ack-grep`), which means that only buffers written to disk will be searched. If no buffers are written to disk, then <strong>[`:Quack`](#user-content-quack)</strong> behaves exactly like <strong>[`:Ack`](#user-content-ack)</strong> and will search all files in the current directory.
    152. 

  152. 

  153. <p align="right"><a name="quack" href="#user-content-quack"><code>:Quack!</code></a></p>
    154. 

  154. 

  155. ### `:Quack! {pattern} {options}`<a name="ferret-quack-pattern-options" href="#user-content-ferret-quack-pattern-options"></a>
    156. 

  156. 

  157. Like <strong>[`:Quack`](#user-content-quack)</strong>, but returns all results irrespective of the value of <strong>[`g:FerretMaxResults`](#user-content-gferretmaxresults)</strong>.
    158. 

  158. 

  159. <p align="right"><a name="acks" href="#user-content-acks"><code>:Acks</code></a></p>
    160. 

  160. 

  161. ### `:Acks /{pattern}/{replacement}/`<a name="ferret-acks-patternreplacement" href="#user-content-ferret-acks-patternreplacement"></a>
    162. 

  162. 

  163. Takes all of the files currently in the <strong>`quickfix`</strong> listing and performs a substitution of all instances of {pattern} (a standard Vim search <strong>`pattern`</strong>) by {replacement}.
    164. 

  164. 

  165. A typical sequence consists of an <strong>[`:Ack`](#user-content-ack)</strong> invocation to populate the <strong>`quickfix`</strong> listing and then <strong>[`:Acks`](#user-content-acks)</strong> (mnemonic: &quot;Ack substitute&quot;) to perform replacements. For example, to replace &quot;foo&quot; with &quot;bar&quot; across all files in the current directory:
    166. 

  166. 

  167. ```
    168. 

  168. :Ack foo
    169. 

  169. :Acks /foo/bar/
    170. 

  170. ```
    171. 

  171. 

  172. The pattern and replacement are passed through literally to Vim's <strong>`:substitute`</strong> command, preserving all characters and escapes, including references to matches in the pattern. For example, the following could be used to swap the order of &quot;foo123&quot; and &quot;bar&quot;:
    173. 

    174. 

  174. ```
    175. 

  175. :Acks /\v(foo\d+)(bar)/\2\1/
    176. 

  176. ```
    177. 

  177. 

  178. <p align="right"><a name="lacks" href="#user-content-lacks"><code>:Lacks</code></a></p>
    179. 

  179. 

  180. ### `:Lacks /{pattern}/{replacement}/`<a name="ferret-lacks-patternreplacement" href="#user-content-ferret-lacks-patternreplacement"></a>
    181. 

  181. 

  182. Takes all of the files in the current <strong>`location-list`</strong> and performs a substitution of all instances of {pattern} by {replacement}. This is an analog of the <strong>[`:Acks`](#user-content-acks)</strong> command, but operates on the <strong>`location-list`</strong> instead of the <strong>`quickfix`</strong> listing.
    183. 

  183. 

  184. <p align="right"><a name="ferretcancelasync" href="#user-content-ferretcancelasync"><code>:FerretCancelAsync</code></a></p>
    185. 

  185. 

  186. ### `:FerretCancelAsync`<a name="ferret-ferretcancelasync" href="#user-content-ferret-ferretcancelasync"></a>
    187. 

  187. 

  188. Cancels any asynchronous search that may be in progress in the background.
    189. 

  189. 

  190. <p align="right"><a name="ferretpullasync" href="#user-content-ferretpullasync"><code>:FerretPullAsync</code></a></p>
    191. 

  191. 

  192. ### `:FerretPullAsync`<a name="ferret-ferretpullasync" href="#user-content-ferret-ferretpullasync"></a>
    193. 

  193. 

  194. Eagerly populates the <strong>`quickfix`</strong> (or <strong>`location-list`</strong>) window with any results that may have been produced by a long-running asynchronous search in progress in the background.
    195. 

  195. 

  196. <p align="right"><a name="qargs" href="#user-content-qargs"><code>:Qargs</code></a></p>
    197. 

  197. 

  198. ### `:Qargs`<a name="ferret-qargs" href="#user-content-ferret-qargs"></a>
    199. 

  199. 

  200. This is a utility function that is used internally when running on older versions of Vim (prior to version 8) but is also generally useful enough to warrant being exposed publicly.
    201. 

  201. 

  202. It takes the files currently in the <strong>`quickfix`</strong> listing and sets them as <strong>`:args`</strong> so that they can be operated on en masse via the <strong>`:argdo`</strong> command.
    203. 

  203. 

  204. <p align="right"><a name="largs" href="#user-content-largs"><code>:Largs</code></a></p>
    205. 

  205. 

  206. ### `:Largs`<a name="ferret-largs" href="#user-content-ferret-largs"></a>
    207. 

  207. 

  208. Just like <strong>[`:Qargs`](#user-content-qargs)</strong>, but applies to the current <strong>`location-list`</strong>.
    209. 

  209. 

  210. It takes the files in the current <strong>`location-list`</strong> and sets them as <strong>`:args`</strong> so that they can be operated on en masse via the <strong>`:argdo`</strong> command.
    211. 

  211. 

  212. 

  213. ## Mappings<a name="ferret-mappings" href="#user-content-ferret-mappings"></a>
    214. 

  214. 

  215. 

  216. ### Circumstances where mappings do not get set up<a name="ferret-circumstances-where-mappings-do-not-get-set-up" href="#user-content-ferret-circumstances-where-mappings-do-not-get-set-up"></a>
    217. 

  217. 

  218. Note that Ferret will not try to set up the &lt;leader&gt; mappings if any of the following are true:
    219. 

  219. 

  220. - A mapping with the same <strong>`{lhs}`</strong> already exists.
    221. 

  221. - An alternative mapping for the same functionality has already been set up from a <strong>`.vimrc`</strong>.
    222. 

  222. - The mapping has been suppressed by setting <strong>[`g:FerretMap`](#user-content-gferretmap)</strong> to 0 in your <strong>`.vimrc`</strong>.
    223. 

  223. 

  224. 

  225. ### Mappings specific to the quickfix window<a name="ferret-mappings-specific-to-the-quickfix-window" href="#user-content-ferret-mappings-specific-to-the-quickfix-window"></a>
    226. 

  226. 

  227. Additionally, Ferret will set up special mappings in <strong>`quickfix`</strong> listings, unless prevented from doing so by <strong>[`g:FerretQFMap`](#user-content-gferretqfmap)</strong>:
    228. 

  228. 

  229. - `d` (<strong>`visual-mode`</strong>): delete visual selection
    230. 

  230. - `dd` (<strong>`Normal-mode`</strong>): delete current line
    231. 

  231. - `d`{motion} (<strong>`Normal-mode`</strong>): delete range indicated by {motion}
    232. 

  232. 

  233. 

  234. ### `<Plug>(FerretAck)`<a name="ferret-plugferretack" href="#user-content-ferret-plugferretack"></a>
    235. 

  235. 

  236. Ferret maps &lt;leader&gt;a to <strong>[`<Plug>(FerretAck)`](#user-content-plugferretack)</strong>, which triggers the <strong>[`:Ack`](#user-content-ack)</strong> command. To use an alternative mapping instead, create a different one in your <strong>`.vimrc`</strong> instead using <strong>`:nmap`</strong>:
    237. 

  237. 

  238. ```
    239. 

  239. " Instead of <leader>a, use <leader>x.
    240. 

  240. nmap <leader>x <Plug>(FerretAck)
    241. 

  241. ```
    242. 

  242. 

  243. 

  244. ### `<Plug>(FerretLack)`<a name="ferret-plugferretlack" href="#user-content-ferret-plugferretlack"></a>
    245. 

  245. 

  246. Ferret maps &lt;leader&gt;l to <strong>[`<Plug>(FerretLack)`](#user-content-plugferretlack)</strong>, which triggers the <strong>[`:Lack`](#user-content-lack)</strong> command. To use an alternative mapping instead, create a different one in your <strong>`.vimrc`</strong> instead using <strong>`:nmap`</strong>:
    247. 

  247. 

  248. ```
    249. 

  249. " Instead of <leader>l, use <leader>y.
    250. 

  250. nmap <leader>y <Plug>(FerretLack)
    251. 

  251. ```
    252. 

  252. 

  253. 

  254. ### `<Plug>(FerretAckWord)`<a name="ferret-plugferretackword" href="#user-content-ferret-plugferretackword"></a>
    255. 

  255. 

  256. Ferret maps &lt;leader&gt;s (mnemonic: &quot;selection) to <strong>[`<Plug>(FerretAckWord)`](#user-content-plugferretackword)</strong>, which uses <strong>[`:Ack`](#user-content-ack)</strong> to search for the word currently under the cursor. To use an alternative mapping instead, create a different one in your <strong>`.vimrc`</strong> instead using <strong>`:nmap`</strong>:
    257. 

  257. 

  258. ```
    259. 

  259. " Instead of <leader>s, use <leader>z.
    260. 

  260. nmap <leader>z <Plug>(FerretAckWord)
    261. 

  261. ```
    262. 

  262. 

  263. 

  264. ### `<Plug>(FerretAcks)`<a name="ferret-plugferretacks" href="#user-content-ferret-plugferretacks"></a>
    265. 

  265. 

  266. Ferret maps &lt;leader&gt;r (mnemonic: &quot;replace&quot;) to <strong>[`<Plug>(FerretAcks)`](#user-content-plugferretacks)</strong>, which triggers the <strong>[`:Acks`](#user-content-acks)</strong> command and fills the prompt with the last search term from Ferret. to use an alternative mapping instead, create a different one in your <strong>`.vimrc`</strong> instead using <strong>`:nmap`</strong>:
    267. 

  267. 

  268. ```
    269. 

  269. " Instead of <leader>r, use <leader>u.
    270. 

  270. nmap <leader>u <Plug>(FerretAcks)
    271. 

  271. ```
    272. 

  272. 

  273. 

  274. ## Options<a name="ferret-options" href="#user-content-ferret-options"></a>
    275. 

  275. 

  276. <p align="right"><a name="gferretnvim" href="#user-content-gferretnvim"><code>g:FerretNvim</code></a></p>
    277. 

  277. 

  278. ### `g:FerretNvim` (boolean, default: 1)<a name="ferret-gferretnvim-boolean-default-1" href="#user-content-ferret-gferretnvim-boolean-default-1"></a>
    279. 

  279. 

  280. Controls whether to use Neovim's <strong>`job-control`</strong> features, when available, to run searches asynchronously. To prevent this from being used, set to 0, in which case Ferret will fall back to the next method in the list (Vim's built-in async primitives -- see <strong>[`g:FerretJob`](#user-content-gferretjob)</strong> -- which are typically not available in Neovim, so will then fall back to the next available method).
    281. 

  281. 

  282. ```
    283. 

  283. let g:FerretNvim=0
    284. 

  284. ```
    285. 

  285. 

  286. <p align="right"><a name="gferretjob" href="#user-content-gferretjob"><code>g:FerretJob</code></a></p>
    287. 

  287. 

  288. ### `g:FerretJob` (boolean, default: 1)<a name="ferret-gferretjob-boolean-default-1" href="#user-content-ferret-gferretjob-boolean-default-1"></a>
    289. 

  289. 

  290. Controls whether to use Vim's <strong>`+job`</strong> feature, when available, to run searches asynchronously. To prevent <strong>`+job`</strong> from being used, set to 0, in which case Ferret will fall back to the next available method.
    291. 

    292. 

  292. ```
    293. 

  293. let g:FerretJob=0
    294. 

  294. ```
    295. 

  295. 

  296. <p align="right"><a name="gferrethlsearch" href="#user-content-gferrethlsearch"><code>g:FerretHlsearch</code></a></p>
    297. 

  297. 

  298. ### `g:FerretHlsearch` (boolean, default: none)<a name="ferret-gferrethlsearch-boolean-default-none" href="#user-content-ferret-gferrethlsearch-boolean-default-none"></a>
    299. 

  299. 

  300. Controls whether Ferret should attempt to highlight the search pattern when running <strong>[`:Ack`](#user-content-ack)</strong> or <strong>[`:Lack`](#user-content-lack)</strong>. If left unset, Ferret will respect the current 'hlsearch' setting. To force highlighting on or off irrespective of 'hlsearch', set <strong>[`g:FerretHlsearch`](#user-content-gferrethlsearch)</strong> to 1 (on) or 0 (off):
    301. 

  301. 

  302. ```
    303. 

  303. let g:FerretHlsearch=0
    304. 

  304. ```
    305. 

  305. 

  306. <p align="right"><a name="gferretackscommand" href="#user-content-gferretackscommand"><code>g:FerretAcksCommand</code></a></p>
    307. 

  307. 

  308. ### `g:FerretAcksCommand` (string, default: "cdo")<a name="ferret-gferretackscommand-string-default-cdo" href="#user-content-ferret-gferretackscommand-string-default-cdo"></a>
    309. 

  309. 

  310. Controls the underlying Vim command that <strong>[`:Acks`](#user-content-acks)</strong> uses to peform substitutions. On versions of Vim that have it, defaults to <strong>`:cdo`</strong>, which means that substitutions will apply to the specific lines currently in the <strong>`quickfix`</strong> listing. Can be set to &quot;cfdo&quot; to instead use <strong>`:cfdo`</strong> (if available), which means that the substitutions will be applied on a per-file basis to all the files in the <strong>`quickfix`</strong> listing. This distinction is important if you have used Ferret's bindings to delete entries from the listing.
    311. 

    312. 

  312. ```
    313. 

  313. let g:FerretAcksCommand='cfdo'
    314. 

  314. ```
    315. 

  315. 

  316. <p align="right"><a name="gferretlackscommand" href="#user-content-gferretlackscommand"><code>g:FerretLacksCommand</code></a></p>
    317. 

  317. 

  318. ### `g:FerretLacksCommand` (string, default: "ldo")<a name="ferret-gferretlackscommand-string-default-ldo" href="#user-content-ferret-gferretlackscommand-string-default-ldo"></a>
    319. 

  319. 

  320. Controls the underlying Vim command that <strong>[`:Lacks`](#user-content-lacks)</strong> uses to peform substitutions. On versions of Vim that have it, defaults to <strong>`:ldo`</strong>, which means that substitutions will apply to the specific lines currently in the <strong>`location-list`</strong>. Can be set to &quot;lfdo&quot; to instead use <strong>`:lfdo`</strong> (if available), which means that the substitutions will be applied on a per-file basis to all the files in the <strong>`location-list`</strong>. This distinction is important if you have used Ferret's bindings to delete entries from the listing.
    321. 

    322. 

  322. ```
    323. 

  323. let g:FerretLacksCommand='lfdo'
    324. 

  324. ```
    325. 

  325. 

  326. <p align="right"><a name="gferretverymagic" href="#user-content-gferretverymagic"><code>g:FerretVeryMagic</code></a></p>
    327. 

  327. 

  328. ### `g:FerretVeryMagic` (boolean, default: 1)<a name="ferret-gferretverymagic-boolean-default-1" href="#user-content-ferret-gferretverymagic-boolean-default-1"></a>
    329. 

  329. 

  330. Controls whether the <strong>[`<Plug>(FerretAck)`](#user-content-plugferretack)</strong> mapping should populate the command line with the <strong>`/\v`</strong> &quot;very magic&quot; marker. Given that the argument passed to <strong>[`:Acks`](#user-content-acks)</strong> is handed straight to Vim, using &quot;very magic&quot; makes it more likely that the (probably Perl-compatible) regular expression used in the initial search can be used directly with Vim's (famously not-Perl-compatible) regular expression engine.
    331. 

    332. 

  332. To prevent the automatic use of <strong>`/\v`</strong>, set this option to 0:
    333. 

  333. 

  334. ```
    335. 

  335. let g:FerretVeryMagic=0
    336. 

  336. ```
    337. 

  337. 

  338. <p align="right"><a name="gferretexecutable" href="#user-content-gferretexecutable"><code>g:FerretExecutable</code></a></p>
    339. 

  339. 

  340. ### `g:FerretExecutable` (string, default: "rg,ag,ack,ack-grep")<a name="ferret-gferretexecutable-string-default-rgagackack-grep" href="#user-content-ferret-gferretexecutable-string-default-rgagackack-grep"></a>
    341. 

  341. 

  342. Ferret will preferentially use `rg`, `ag` and finally `ack`/`ack-grep` (in that order, using the first found executable), however you can force your preference for a specific tool to be used by setting an override in your <strong>`.vimrc`</strong>. Valid values are a comma-separated list of &quot;rg&quot;, &quot;ag&quot;, &quot;ack&quot; or &quot;ack-grep&quot;. If no requested executable exists, Ferret will fall-back to the next in the default list.
    343. 

  343. 

  344. Example:
    345. 

  345. 

  346. ```
    347. 

  347. " Prefer `ag` over `rg`.
    348. 

  348. let g:FerretExecutable='ag,rg'
    349. 

  349. ```
    350. 

  350. 

  351. <p align="right"><a name="gferretexecutablearguments" href="#user-content-gferretexecutablearguments"><code>g:FerretExecutableArguments</code></a></p>
    352. 

  352. 

  353. ### `g:FerretExecutableArguments` (dict, default: {})<a name="ferret-gferretexecutablearguments-dict-default-" href="#user-content-ferret-gferretexecutablearguments-dict-default-"></a>
    354. 

  354. 

  355. Allows you to override the default arguments that get passed to the underlying search executables. For example, to add `-s` to the default arguments passed to `ack` (`--column --with-filename`):
    356. 

  356. 

  357. ```
    358. 

  358. let g:FerretExecutableArguments = {
    359. 

  359.   \   'ack': '--column --with-filename -s'
    360. 

  360.   \ }
    361. 

  361. ```
    362. 

  362. 

  363. To find out the default arguments for a given executable, see <strong>[`ferret#get_default_arguments()`](#user-content-ferretgetdefaultarguments)</strong>.
    364. 

  364. 

  365. <p align="right"><a name="gferretmaxresults" href="#user-content-gferretmaxresults"><code>g:FerretMaxResults</code></a></p>
    366. 

  366. 

  367. ### `g:FerretMaxResults` (number, default: 100000)<a name="ferret-gferretmaxresults-number-default-100000" href="#user-content-ferret-gferretmaxresults-number-default-100000"></a>
    368. 

  368. 

  369. Controls the maximum number of results Ferret will attempt to gather before displaying the results. Note that this only applies when searching asynchronously; that is, on recent versions of Vim with <strong>`+job`</strong> support and when <strong>[`g:FerretJob`](#user-content-gferretjob)</strong> is not set to 0.
    370. 

  370. 

  371. The intent of this option is to prevent runaway search processes that produce huge volumes of output (for example, searching for a common string like &quot;test&quot; inside a <strong>`$HOME`</strong> directory containing millions of files) from locking up Vim.
    372. 

  372. 

  373. In the event that Ferret aborts a search that has hit the <strong>[`g:FerretMaxResults`](#user-content-gferretmaxresults)</strong> limit, a message will be printed prompting users to run the search again with <strong>[`:Ack!`](#user-content-ack)</strong> or <strong>[`:Lack!`](#user-content-lack)</strong> if they want to bypass the limit.
    374. 

  374. 

  375. <p align="right"><a name="gferretautojump" href="#user-content-gferretautojump"><code>g:FerretAutojump</code></a></p>
    376. 

  376. 

  377. ### `g:FerretAutojump` (number, default: 1)<a name="ferret-gferretautojump-number-default-1" href="#user-content-ferret-gferretautojump-number-default-1"></a>
    378. 

  378. 

  379. Controls whether Ferret will automatically jump to the first found match.
    380. 

  380. 

  381. - Set to 0, Ferret will show the search results but perform no jump.
    382. 

  382. - Set to 1 (the default), Ferret will show the search results and focus the result listing.
    383. 

  383. - Set to 2, Ferret will show the search results and jump to the first found match.
    384. 

  384. 

  385. Example override:
    386. 

  386. 

  387. ```
    388. 

  388. let g:FerretAutojump=2
    389. 

  389. ```
    390. 

  390. 

  391. <p align="right"><a name="gferretqfhandler" href="#user-content-gferretqfhandler"><code>g:FerretQFHandler</code></a></p>
    392. 

  392. 

  393. ### `g:FerretQFHandler` (string, default: "botright copen")<a name="ferret-gferretqfhandler-string-default-botright-copen" href="#user-content-ferret-gferretqfhandler-string-default-botright-copen"></a>
    394. 

  394. 

  395. Allows you to override the mechanism that opens the <strong>`quickfix`</strong> window to display search results.
    396. 

  396. 

  397. <p align="right"><a name="gferretllhandler" href="#user-content-gferretllhandler"><code>g:FerretLLHandler</code></a></p>
    398. 

  398. 

  399. ### `g:FerretLLHandler` (string, default: "lopen")<a name="ferret-gferretllhandler-string-default-lopen" href="#user-content-ferret-gferretllhandler-string-default-lopen"></a>
    400. 

  400. 

  401. Allows you to override the mechanism that opens the <strong>`location-list`</strong> window to display search results.
    402. 

  402. 

  403. <p align="right"><a name="gferretqfoptions" href="#user-content-gferretqfoptions"><code>g:FerretQFOptions</code></a></p>
    404. 

  404. 

  405. ### `g:FerretQFOptions` (boolean, default: 1)<a name="ferret-gferretqfoptions-boolean-default-1" href="#user-content-ferret-gferretqfoptions-boolean-default-1"></a>
    406. 

  406. 

  407. Controls whether to set up setting overrides for <strong>`quickfix`</strong> windows. These are various settings, such as <strong>`norelativenumber`</strong>, <strong>`nolist`</strong> and <strong>`nowrap`</strong>, that are intended to make the <strong>`quickfix`</strong> window, which is typically very small relative to other windows, more usable.
    408. 

  408. 

  409. A full list of overridden settings can be found in <strong>[`ferret-overrides`](#user-content-ferret-overrides)</strong>.
    410. 

  410. 

  411. To prevent the custom settings from being applied, set <strong>[`g:FerretQFOptions`](#user-content-gferretqfoptions)</strong> to 0:
    412. 

  412. 

  413. ```
    414. 

  414. let g:FerretQFOptions=0
    415. 

  415. ```
    416. 

  416. 

  417. <p align="right"><a name="gferretqfmap" href="#user-content-gferretqfmap"><code>g:FerretQFMap</code></a></p>
    418. 

  418. 

  419. ### `g:FerretQFMap` (boolean, default: 1)<a name="ferret-gferretqfmap-boolean-default-1" href="#user-content-ferret-gferretqfmap-boolean-default-1"></a>
    420. 

  420. 

  421. Controls whether to set up mappings in the <strong>`quickfix`</strong> results window and <strong>`location-list`</strong> for deleting results. The mappings include:
    422. 

  422. 

  423. - `d` (<strong>`visual-mode`</strong>): delete visual selection
    424. 

  424. - `dd` (<strong>`Normal-mode`</strong>): delete current line
    425. 

  425. - `d`{motion} (<strong>`Normal-mode`</strong>): delete range indicated by {motion}
    426. 

  426. 

  427. To prevent these mappings from being set up, set to 0:
    428. 

  428. 

  429. ```
    430. 

  430. let g:FerretQFMap=0
    431. 

  431. ```
    432. 

  432. 

  433. <p align="right"><a name="gferretloaded" href="#user-content-gferretloaded"><code>g:FerretLoaded</code></a></p>
    434. 

  434. 

  435. ### `g:FerretLoaded` (any, default: none)<a name="ferret-gferretloaded-any-default-none" href="#user-content-ferret-gferretloaded-any-default-none"></a>
    436. 

  436. 

  437. To prevent Ferret from being loaded, set <strong>[`g:FerretLoaded`](#user-content-gferretloaded)</strong> to any value in your <strong>`.vimrc`</strong>. For example:
    438. 

  438. 

  439. ```
    440. 

  440. let g:FerretLoaded=1
    441. 

  441. ```
    442. 

  442. 

  443. <p align="right"><a name="gferretlazyinit" href="#user-content-gferretlazyinit"><code>g:FerretLazyInit</code></a></p>
    444. 

  444. 

  445. ### `g:FerretLazyInit` (boolean, default: 1)<a name="ferret-gferretlazyinit-boolean-default-1" href="#user-content-ferret-gferretlazyinit-boolean-default-1"></a>
    446. 

  446. 

  447. In order to minimize impact on Vim start-up time Ferret will initialize itself lazily on first use by default. If you wish to force immediate initialization (for example, to cause <strong>`'grepprg'`</strong> and <strong>`'grepformat'`</strong> to be set as soon as Vim launches), then set <strong>[`g:FerretLazyInit`](#user-content-gferretlazyinit)</strong> to 0 in your <strong>`.vimrc`</strong>:
    448. 

  448. 

  449. ```
    450. 

  450. let g:FerrerLazyInit=0
    451. 

  451. ```
    452. 

  452. 

  453. <p align="right"><a name="gferretackwordword" href="#user-content-gferretackwordword"><code>g:FerretAckWordWord</code></a></p>
    454. 

  454. 

  455. ### `g:FerretAckWordWord` (boolean, default: 0)<a name="ferret-gferretackwordword-boolean-default-0" href="#user-content-ferret-gferretackwordword-boolean-default-0"></a>
    456. 

  456. 

  457. When set to 1, passes the `-w` option to the underlying search tool whenever <strong>[`<Plug>(FerretAckWord)`](#user-content-plugferretackword)</strong> is pressed. This forces the tool to match only on word boundaries (ie. analagous to Vim's <strong>`star`</strong> mapping).
    458. 

    459. 

  459. The default is 0, which means the `-w` option is not passed and matches need not occur on word boundaries (ie. analagous to Vim's <strong>`gstar`</strong> mapping).
    460. 

    461. 

  461. To override the default:
    462. 

  462. 

  463. ```
    464. 

  464. let g:FerretAckWordWord=1
    465. 

  465. ```
    466. 

  466. 

  467. <p align="right"><a name="gferretmap" href="#user-content-gferretmap"><code>g:FerretMap</code></a></p>
    468. 

  468. 

  469. ### `g:FerretMap` (boolean, default: 1)<a name="ferret-gferretmap-boolean-default-1" href="#user-content-ferret-gferretmap-boolean-default-1"></a>
    470. 

  470. 

  471. Controls whether to set up the Ferret mappings, such as <strong>[`<Plug>(FerretAck)`](#user-content-plugferretack)</strong> (see <strong>[`ferret-mappings`](#user-content-ferret-mappings)</strong> for a full list). To prevent any mapping from being configured, set to 0:
    472. 

  472. 

  473. ```
    474. 

  474. let g:FerretMap=0
    475. 

  475. ```
    476. 

  476. 

  477. <p align="right"><a name="gferretqfcommands" href="#user-content-gferretqfcommands"><code>g:FerretQFCommands</code></a></p>
    478. 

  478. 

  479. ### `g:FerretQFCommands` (boolean, default: 1)<a name="ferret-gferretqfcommands-boolean-default-1" href="#user-content-ferret-gferretqfcommands-boolean-default-1"></a>
    480. 

  480. 

  481. Controls whether to set up custom versions of the <strong>`quickfix`</strong> commands, <strong>`:cn`</strong>, <strong>`:cnf`</strong>, <strong>`:cp`</strong> an <strong>`:cpf`</strong>. These overrides vertically center the match within the viewport on each jump. To prevent the custom versions from being configured, set to 0:
    482. 

  482. 

  483. ```
    484. 

  484. let g:FerretQFCommands=0
    485. 

  485. ```
    486. 

  486. 

  487. <p align="right"><a name="gferretformat" href="#user-content-gferretformat"><code>g:FerretFormat</code></a></p>
    488. 

  488. 

  489. ### `g:FerretFormat` (string, default: "%f:%l:%c:%m")<a name="ferret-gferretformat-string-default-flcm" href="#user-content-ferret-gferretformat-string-default-flcm"></a>
    490. 

  490. 

  491. Sets the '<strong>`grepformat`</strong>' used by Ferret.
    492. 

  492. 

  493. 

  494. ## Functions<a name="ferret-functions" href="#user-content-ferret-functions"></a>
    495. 

  495. 

  496. <p align="right"><a name="ferretgetdefaultarguments" href="#user-content-ferretgetdefaultarguments"><code>ferret#get_default_arguments()</code></a></p>
    497. 

  497. 

  498. ### `ferret#get_default_arguments()`<a name="ferret-ferretgetdefaultarguments" href="#user-content-ferret-ferretgetdefaultarguments"></a>
    499. 

  499. 

  500. Call this with an executable name to find out the default arguments that will be passed when invoking that executable. For example:
    501. 

  501. 

  502. ```
    503. 

  503. echo ferret#get_default_arguments('rg')
    504. 

  504. ```
    505. 

  505. 

  506. This may be useful if you wish to extend or otherwise modify the arguments by setting <strong>[`g:FerretExecutableArguments`](#user-content-gferretexecutablearguments)</strong>.
    507. 

  507. 

  508. 

  509. ## Custom autocommands<a name="ferret-custom-autocommands" href="#user-content-ferret-custom-autocommands"></a>
    510. 

  510. 

  511. <p align="right"><a name="ferretdidwrite" href="#user-content-ferretdidwrite"><code>FerretDidWrite</code></a> <a name="ferretwillwrite" href="#user-content-ferretwillwrite"><code>FerretWillWrite</code></a></p>
    512. 

  512. For maximum compatibility with other plug-ins, Ferret runs the following &quot;User&quot; autocommands before and after running the file writing operations during <strong>[`:Acks`](#user-content-acks)</strong> or <strong>[`:Lacks`](#user-content-lacks)</strong>:
    513. 

  513. 

  514. - FerretWillWrite
    515. 

  515. - FerretDidWrite
    516. 

  516. 

  517. For example, to call a pair of custom functions in response to these events, you might do:
    518. 

  518. 

  519. ```
    520. 

  520. autocmd! User FerretWillWrite
    521. 

  521. autocmd User FerretWillWrite call CustomWillWrite()
    522. 

  522. autocmd! User FerretDidWrite
    523. 

  523. autocmd User FerretDidWrite call CustomDidWrite()
    524. 

  524. ```
    525. 

  525. 

  526. 

  527. ## Overrides<a name="ferret-overrides" href="#user-content-ferret-overrides"></a>
    528. 

  528. 

  529. Ferret overrides the 'grepformat' and 'grepprg' settings, preferentially setting `rg`, `ag`, `ack` or `ack-grep` as the 'grepprg' (in that order) and configuring a suitable 'grepformat'.
    530. 

  530. 

  531. Additionally, Ferret includes an <strong>`ftplugin`</strong> for the <strong>`quickfix`</strong> listing that adjusts a number of settings to improve the usability of search results.
    532. 

  532. 

  533. <p align="right"><a name="ferret-nolist" href="#user-content-ferret-nolist"><code>ferret-nolist</code></a></p>
    534. 

  534. 

  535. ### 'nolist'<a name="ferret-nolist" href="#user-content-ferret-nolist"></a>
    536. 

  536. 

  537. Turned off to reduce visual clutter in the search results, and because 'list' is most useful in files that are being actively edited, which is not the case for <strong>`quickfix`</strong> results.
    538. 

  538. 

  539. <p align="right"><a name="ferret-norelativenumber" href="#user-content-ferret-norelativenumber"><code>ferret-norelativenumber</code></a></p>
    540. 

  540. 

  541. ### 'norelativenumber'<a name="ferret-norelativenumber" href="#user-content-ferret-norelativenumber"></a>
    542. 

  542. 

  543. Turned off, because it is more useful to have a sense of absolute progress through the results list than to have the ability to jump to nearby results (especially seeing as the most common operations are moving to the next or previous file, which are both handled nicely by <strong>`:cnf`</strong> and <strong>`:cpf`</strong> respectively).
    544. 

  544. 

  545. <p align="right"><a name="ferret-nowrap" href="#user-content-ferret-nowrap"><code>ferret-nowrap</code></a></p>
    546. 

  546. 

  547. ### 'nowrap'<a name="ferret-nowrap" href="#user-content-ferret-nowrap"></a>
    548. 

  548. 

  549. Turned off to avoid ugly wrapping that makes the results list hard to read, and because in search results, the most relevant information is the filename, which is on the left and is usually visible even without wrapping.
    550. 

  550. 

  551. <p align="right"><a name="ferret-number" href="#user-content-ferret-number"><code>ferret-number</code></a></p>
    552. 

  552. 

  553. ### 'number'<a name="ferret-number" href="#user-content-ferret-number"></a>
    554. 

  554. 

  555. Turned on to give a sense of absolute progress through the results.
    556. 

  556. 

  557. <p align="right"><a name="ferret-scrolloff" href="#user-content-ferret-scrolloff"><code>ferret-scrolloff</code></a></p>
    558. 

  558. 

  559. ### 'scrolloff'<a name="ferret-scrolloff" href="#user-content-ferret-scrolloff"></a>
    560. 

  560. 

  561. Set to 0 because the <strong>`quickfix`</strong> listing is usually small by default, so trying to keep the current line away from the edge of the viewpoint is futile; by definition it is usually near the edge.
    562. 

  562. 

  563. <p align="right"><a name="ferret-nocursorline" href="#user-content-ferret-nocursorline"><code>ferret-nocursorline</code></a></p>
    564. 

  564. 

  565. ### 'nocursorline'<a name="ferret-nocursorline" href="#user-content-ferret-nocursorline"></a>
    566. 

  566. 

  567. Turned off to reduce visual clutter.
    568. 

  568. 

  569. To prevent any of these <strong>`quickfix`</strong>-specific overrides from being set up, you can set <strong>[`g:FerretQFOptions`](#user-content-gferretqfoptions)</strong> to 0 in your <strong>`.vimrc`</strong>:
    570. 

  570. 

  571. ```
    572. 

  572. let g:FerretQFOptions=0
    573. 

  573. ```
    574. 

  574. 

  575. 

  576. ## Troubleshooting<a name="ferret-troubleshooting" href="#user-content-ferret-troubleshooting"></a>
    577. 

  577. 

  578. <p align="right"><a name="ferret-quotes" href="#user-content-ferret-quotes"><code>ferret-quotes</code></a></p>
    579. 

  579. 

  580. ### Ferret fails to find patterns containing spaces<a name="ferret-ferret-fails-to-find-patterns-containing-spaces" href="#user-content-ferret-ferret-fails-to-find-patterns-containing-spaces"></a>
    581. 

  581. 

  582. As described in the documentation for <strong>[`:Ack`](#user-content-ack)</strong>, the search pattern is passed through as-is to the underlying search command, and no escaping is required other than preceding spaces by a single backslash.
    583. 

  583. 

  584. So, to find &quot;foo bar&quot;, you would search like:
    585. 

  585. 

  586. ```
    587. 

  587. :Ack foo\ bar
    588. 

  588. ```
    589. 

  589. 

  590. Unescaped spaces in the search are treated as argument separators, so a command like the following means pass the `-w` option through, search for pattern &quot;foo&quot;, and limit search to the &quot;bar&quot; directory:
    591. 

  591. 

  592. ```
    593. 

  593. :Ack -w foo bar
    594. 

  594. ```
    595. 

  595. 

  596. Note that including quotes will not do what you intend.
    597. 

  597. 

  598. ```
    599. 

  599.  " Search for '"foo' in the 'bar"' directory:
    600. 

  600.  :Ack "foo bar"
    601. 

    602. 

  602.  " Search for "'foo' in the "bar'" directory:
    603. 

  603.  :Ack 'foo bar'
    604. 

  604. ```
    605. 

  605. 

  606. This approach to escaping is taken in order to make it straightfoward to use powerful Perl-compatible regular expression syntax in an unambiguous way without having to worry about shell escaping rules:
    607. 

  607. 

  608. ```
    609. 

  609. :Ack \blog\((['"]).*?\1\) -i --ignore-dir=src/vendor src dist build
    610. 

  610. ```
    611. 

  611. 

  612. 

  613. ## FAQ<a name="ferret-faq" href="#user-content-ferret-faq"></a>
    614. 

  614. 

  615. 

  616. ### Why do Ferret commands start with "Ack", "Lack" and so on?<a name="ferret-why-do-ferret-commands-start-with-ack-lack-and-so-on" href="#user-content-ferret-why-do-ferret-commands-start-with-ack-lack-and-so-on"></a>
    617. 

  617. 

  618. Ferret was originally the thinnest of wrappers (7 lines of code in my <strong>`.vimrc`</strong>) around `ack`. The earliest traces of it can be seen in the initial commit to my dotfiles repo in May, 2009 (https://wincent.com/h).
    619. 

  619. 

  620. So, even though Ferret has a new name now and actually prefers `rg` then `ag` over `ack`/`ack-grep` when available, I prefer to keep the command names intact and benefit from years of accumulated muscle-memory.
    621. 

  621. 

  622. 

  623. ## Related<a name="ferret-related" href="#user-content-ferret-related"></a>
    624. 

  624. 

  625. Just as Ferret aims to improve the multi-file search and replace experience, Loupe does the same for within-file searching:
    626. 

  626. 

  627. https://github.com/wincent/loupe
    628. 

  628. 

  629. 

  630. ## Website<a name="ferret-website" href="#user-content-ferret-website"></a>
    631. 

  631. 

  632. The official Ferret source code repo is at:
    633. 

  633. 

  634. http://git.wincent.com/ferret.git
    635. 

  635. 

  636. A mirror exists at:
    637. 

  637. 

  638. https://github.com/wincent/ferret
    639. 

  639. 

  640. Official releases are listed at:
    641. 

  641. 

  642. http://www.vim.org/scripts/script.php?script_id=5220
    643. 

  643. 

  644. 

  645. ## License<a name="ferret-license" href="#user-content-ferret-license"></a>
    646. 

  646. 

  647. Copyright 2015-present Greg Hurrell. All rights reserved.
    648. 

  648. 

  649. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
    650. 

  650. 

  651. 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
    652. 

  652. 

  653. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
    654. 

  654. 

  655. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS &quot;AS IS&quot; AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
    656. 

  656. 

  657. 

  658. ## Development<a name="ferret-development" href="#user-content-ferret-development"></a>
    659. 

  659. 

  660. 

  661. ### Contributing patches<a name="ferret-contributing-patches" href="#user-content-ferret-contributing-patches"></a>
    662. 

  662. 

  663. Patches can be sent via mail to greg@hurrell.net, or as GitHub pull requests at: https://github.com/wincent/ferret/pulls
    664. 

  664. 

  665. 

  666. ### Cutting a new release<a name="ferret-cutting-a-new-release" href="#user-content-ferret-cutting-a-new-release"></a>
    667. 

  667. 

  668. At the moment the release process is manual:
    669. 

  669. 

  670. - Perform final sanity checks and manual testing
    671. 

  671. - Update the <strong>[`ferret-history`](#user-content-ferret-history)</strong> section of the documentation
    672. 

  672. - Verify clean work tree:
    673. 

  673. 

  674. ```
    675. 

  675. git status
    676. 

  676. ```
    677. 

  677. 

  678. - Tag the release:
    679. 

  679. 

  680. ```
    681. 

  681. git tag -s -m "$VERSION release" $VERSION
    682. 

  682. ```
    683. 

  683. 

  684. - Publish the code:
    685. 

  685. 

  686. ```
    687. 

  687. git push origin master --follow-tags
    688. 

  688. git push github master --follow-tags
    689. 

  689. ```
    690. 

  690. 

  691. - Produce the release archive:
    692. 

  692. 

  693. ```
    694. 

  694. git archive -o ferret-$VERSION.zip HEAD -- .
    695. 

  695. ```
    696. 

  696. 

  697. - Upload to http://www.vim.org/scripts/script.php?script_id=5220
    698. 

  698. 

  699. 

  700. ## Authors<a name="ferret-authors" href="#user-content-ferret-authors"></a>
    701. 

  701. 

  702. Ferret is written and maintained by Greg Hurrell &lt;greg@hurrell.net&gt;.
    703. 

  703. 

  704. Other contributors that have submitted patches include (in alphabetical order):
    705. 

  705. 

  706. - Daniel Silva
    707. 

  707. - Filip Szymański
    708. 

  708. - Joe Lencioni
    709. 

  709. - Jon Parise
    710. 

  710. - Nelo Wallus
    711. 

  711. - Tom Dooner
    712. 

  712. - Vaibhav Sagar
    713. 

  713. - Yoni Weill
    714. 

  714. 

  715. This list produced with:
    716. 

  716. 

  717. ```
    718. 

  718. :read !git shortlog -s HEAD | grep -v 'Greg Hurrell' | cut -f 2-3 | sed -e 's/^/- /'
    719. 

  719. ```
    720. 

  720. 

  721. 

  722. ## History<a name="ferret-history" href="#user-content-ferret-history"></a>
    723. 

  723. 

  724. 

  725. ### master (not yet released)<a name="ferret-master-not-yet-released" href="#user-content-ferret-master-not-yet-released"></a>
    726. 

  726. 

  727. - Add <strong>[`g:FerretAckWordWord`](#user-content-gferretackwordword)</strong> setting, to pass `-w` to the underlying search tool when <strong>[`<Plug>(FerretAckWord)`](#user-content-plugferretackword)</strong> is pressed (https://github.com/wincent/ferret/issues/66).
    728. 

  728. - Use `:normal!` instead of <strong>`:normal`</strong> to avoid running custom mappings (patch from Yoni Weill, https://github.com/wincent/ferret/pull/67).
    729. 

  729. - Append a trailing slash when autocompleting a directory name (https://github.com/wincent/ferret/issues/69).
    730. 

  730. 

  731. 

  732. ### 5.0 (8 June 2019)<a name="ferret-50-8-june-2019" href="#user-content-ferret-50-8-june-2019"></a>
    733. 

  733. 

  734. - The <strong>[`<Plug>(FerretAcks)`](#user-content-plugferretacks)</strong> mapping now uses <strong>`/\v`</strong> &quot;very magic&quot; mode by default. This default can be changed using the <strong>[`g:FerretVeryMagic`](#user-content-gferretverymagic)</strong> option.
    735. 

  735. - <strong>[`:Acks`](#user-content-acks)</strong> now preferentially uses <strong>`:cdo`</strong> (rather than <strong>`:cfdo`</strong>) to make replacements, which means that it no longer operates on a per-file level and instead targets individual entries within the <strong>`quickfix`</strong> window. This is relevant if you've used Ferrets mappings to delete entries from the window. The old behavior can be restored with the <strong>[`g:FerretAcksCommand`](#user-content-gferretackscommand)</strong> option.
    736. 

  736. - Ferret now has a <strong>[`:Lacks`](#user-content-lacks)</strong> command, an analog to <strong>[`:Acks`](#user-content-acks)</strong> which applies to the <strong>`location-list`</strong>.
    737. 

  737. - Likewise, Ferret now has a <strong>[`:Largs`](#user-content-largs)</strong> command, analogous to <strong>[`:Qargs`](#user-content-qargs)</strong>, which applies to the <strong>`location-list`</strong> instead of the <strong>`quickfix`</strong> window.
    738. 

  738. - The Ferret bindings that are set-up in the <strong>`quickfix`</strong> window when <strong>[`g:FerretQFMap`](#user-content-gferretqfmap)</strong> is enabled now also apply to the <strong>`location-list`</strong>.
    739. 

  739. 

  740. 

  741. ### 4.1 (31 January 2019)<a name="ferret-41-31-january-2019" href="#user-content-ferret-41-31-january-2019"></a>
    742. 

  742. 

  743. - Added <strong>[`:Quack`](#user-content-quack)</strong> command, analogous to <strong>[`:Ack`](#user-content-ack)</strong> but scoped to the files currently listed in the <strong>`quickfix`</strong> window.
    744. 

  744. - Fixed option autocompletion.
    745. 

  745. 

  746. 

  747. ### 4.0.2 (11 January 2019)<a name="ferret-402-11-january-2019" href="#user-content-ferret-402-11-january-2019"></a>
    748. 

  748. 

  749. - Restore compatibility with versions of `rg` prior to v0.8 (https://github.com/wincent/ferret/issues/59).
    750. 

  750. 

  751. 

  752. ### 4.0.1 (8 January 2019)<a name="ferret-401-8-january-2019" href="#user-content-ferret-401-8-january-2019"></a>
    753. 

  753. 

  754. - Make <strong>[`:Acks`](#user-content-acks)</strong> behavior the same irrespective of the <strong>`'gdefault'`</strong> setting.
    755. 

  755. 

  756. 

  757. ### 4.0 (25 December 2018)<a name="ferret-40-25-december-2018" href="#user-content-ferret-40-25-december-2018"></a>
    758. 

  758. 

  759. - Try to avoid &quot;press ENTER to continue&quot; prompts.
    760. 

  760. - Put search term in <strong>`w:quickfix_title`</strong> for use in statuslines (https://github.com/wincent/ferret/pull/57).
    761. 

  761. - Add <strong>[`g:FerretExecutableArguments`](#user-content-gferretexecutablearguments)</strong> and <strong>[`ferret#get_default_arguments()`](#user-content-ferretgetdefaultarguments)</strong> (https://github.com/wincent/ferret/pull/46).
    762. 

  762. 

  763. 

  764. ### 3.0.3 (23 March 2018)<a name="ferret-303-23-march-2018" href="#user-content-ferret-303-23-march-2018"></a>
    765. 

  765. 

  766. - Fix for <strong>[`:Lack`](#user-content-lack)</strong> results opening in quickfix listing in Neovim (https://github.com/wincent/ferret/issues/47).
    767. 

  767. 

  768. 

  769. ### 3.0.2 (25 October 2017)<a name="ferret-302-25-october-2017" href="#user-content-ferret-302-25-october-2017"></a>
    770. 

  770. 

  771. - Fix broken <strong>[`:Back`](#user-content-back)</strong> and <strong>[`:Black`](#user-content-black)</strong> commands (https://github.com/wincent/ferret/issues/48).
    772. 

  772. 

  773. 

  774. ### 3.0.1 (24 August 2017)<a name="ferret-301-24-august-2017" href="#user-content-ferret-301-24-august-2017"></a>
    775. 

  775. 

  776. - Fix failure to handle search patterns containing multiple escaped spaces (https://github.com/wincent/ferret/issues/49).
    777. 

  777. 

  778. 

  779. ### 3.0 (13 June 2017)<a name="ferret-30-13-june-2017" href="#user-content-ferret-30-13-june-2017"></a>
    780. 

  780. 

  781. - Improve handling of backslash escapes (https://github.com/wincent/ferret/issues/41).
    782. 

  782. - Add <strong>[`g:FerretAutojump`](#user-content-gferretautojump)</strong>.
    783. 

  783. - Drop support for vim-dispatch.
    784. 

  784. 

  785. 

  786. ### 2.0 (6 June 2017)<a name="ferret-20-6-june-2017" href="#user-content-ferret-20-6-june-2017"></a>
    787. 

  787. 

  788. - Add support for Neovim, along with <strong>[`g:FerretNvim`](#user-content-gferretnvim)</strong> setting.
    789. 

  789. 

  790. 

  791. ### 1.5 "Cinco de Cuatro" (4 May 2017)<a name="ferret-15-cinco-de-cuatro-4-may-2017" href="#user-content-ferret-15-cinco-de-cuatro-4-may-2017"></a>
    792. 

  792. 

  793. - Improvements to the handling of very large result sets (due to wide lines or many results).
    794. 

  794. - Added <strong>[`g:FerretLazyInit`](#user-content-gferretlazyinit)</strong>.
    795. 

  795. - Added missing documentation for <strong>[`g:FerretJob`](#user-content-gferretjob)</strong>.
    796. 

  796. - Added <strong>[`g:FerretMaxResults`](#user-content-gferretmaxresults)</strong>.
    797. 

  797. - Added feature-detection for `rg` and `ag`, allowing Ferret to gracefully work with older versions of those tools that do not support all desired command-line switches.
    798. 

  798. 

  799. 

  800. ### 1.4 (21 January 2017)<a name="ferret-14-21-january-2017" href="#user-content-ferret-14-21-january-2017"></a>
    801. 

  801. 

  802. - Drop broken support for `grep`, printing a prompt to install `rg`, `ag`, or `ack`/`ack-grep` instead.
    803. 

  803. - If an `ack` executable is not found, search for `ack-grep`, which is the name used on Debian-derived distros.
    804. 

  804. 

  805. 

  806. ### 1.3 (8 January 2017)<a name="ferret-13-8-janua…
    807.

Large files files are truncated, but you can click here to view the full file