Skip to content

Commit 620445b

Browse files
committed
docs(readme): some typo and cleaned up some examples
Supersedes #66
1 parent 9299235 commit 620445b

File tree

1 file changed

+2
-11
lines changed

1 file changed

+2
-11
lines changed

README.md

Lines changed: 2 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -201,8 +201,8 @@ These mappings are disabled by default. (config: `mappings.extended`)
201201
`gcw` - Toggle from the current cursor position to the next word
202202
`gc$` - Toggle from the current cursor position to the end of line
203203
`gc}` - Toggle until the next blank line
204-
`gc5l` - Toggle 5 lines after the current cursor
205-
`gc8k` - Toggle 8 lines before the current cursor
204+
`gc5l` - Toggle 5 lines after the current cursor position
205+
`gc8k` - Toggle 8 lines before the current cursor position
206206
`gcip` - Toggle inside of paragraph
207207
`gca}` - Toggle around curly brackets
208208
@@ -243,15 +243,6 @@ There are two hook methods i.e `pre_hook` and `post_hook` which are called befor
243243
- `pre_hook` - This method is called with a [`ctx`](#comment-context) argument before comment/uncomment is started. It can be used to return a custom `commentstring` which will be used for comment/uncomment the lines. You can use something like [nvim-ts-context-commentstring](https://github.com/JoosepAlviste/nvim-ts-context-commentstring) to compute the commentstring using treesitter.
244244

245245
```lua
246-
247-
{
248-
---@param ctx Ctx
249-
pre_hook = function(ctx)
250-
return require('ts_context_commentstring.internal').calculate_commentstring()
251-
end
252-
}
253-
254-
-- OR with some spicy logic
255246
-- NOTE: The example below is a proper integration and it is RECOMMENDED.
256247
{
257248
---@param ctx Ctx

0 commit comments

Comments
 (0)