diff options
| author | Surav Shrestha <148448735+suravkshrestha@users.noreply.github.com> | 2023-10-19 21:46:28 +0545 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-10-19 09:01:28 -0700 |
| commit | 55abaaa9ed4684cd9ba8f0c062379be6cf41b8f3 (patch) | |
| tree | ef529070a9a9e86f819fdd0220ede4b96de1efd0 /doc | |
| parent | 2e8b826cb4af5cf36b5febc5e7a71d3284f161f2 (diff) | |
docs: fix typo in doc/advanced_topics.md (#151)
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/advanced_topics.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/advanced_topics.md b/doc/advanced_topics.md index ff3cc2b..71aadf9 100644 --- a/doc/advanced_topics.md +++ b/doc/advanced_topics.md @@ -16,7 +16,7 @@ What conform does differently is it leverages `:help vim.diff`, Neovim's lua bin ## Range formatting -When a formatting tool doesn't have built-in support for range formatting, conform will attempt to "fake it" when requested. This is necessarily a **best effort** operation and is **not** guaranteed to be correct or error-free, however in _most_ cases it should produce acceptible results. +When a formatting tool doesn't have built-in support for range formatting, conform will attempt to "fake it" when requested. This is necessarily a **best effort** operation and is **not** guaranteed to be correct or error-free, however in _most_ cases it should produce acceptable results. The way this "aftermarket" range formatting works is conform will format the entire buffer as per usual, but during the diff process it will discard diffs that fall outside of the selected range. This usually approximates a correct result, but as you can guess it's possible for the formatting to exceed the range (if the diff covering the range is large) or for the results to be incorrect (if the formatting changes require two diffs in different locations to be semantically correct). |