Johnny M. Salas

Given this plugin scope is bigger than just code (ie: it supports unicode). I think title case is in fact a good candidate for the default list of keymaps.

That's totally feasible. In fact, As Grzegorz, coerce's author, mentions in its readme coerce is based on text-case and the method for registering custom cases exists in both. It will...

`path/case` is built-in. I hadn't noticed there were some cases with no matching triggers. That's a bug! at least we should make it explicit in the readme. But no worries,...

By the way, keeping this issue open. Will add "Custom Case support" this weekend

On a second thought, please correct me, there is no much sense on using LSP case change for path case. Perhaps ga/ is a good keybindings

Appreciate your kind words. I've been considering the different edge cases of this implementation. Specifically, on adding this behavior to one of the existing methods. LSP rename is a better...

@tummetott it can be a new function as you suggested. Do you think you can create a PR? That one sounds easy since it is a new feature (non breaking...

Something that resonated to me in the issue is there are too many keybindings, I didn't notice it until stopped programming for a while and then came back, there is...

This plugin uses [buf_request](https://github.com/johmsalas/text-case.nvim/blob/acd6178ffcf728c82036c7064630ff40f4c9ae82/lua/textcase/plugin/conversion.lua#L20), which seems to be deprecated o.O It should be replace by `buf_request_all({bufnr}, {method}, {params}, {handler})` that receives a callback (handler) with the result after attempting the...

Related: https://github.com/johmsalas/text-case.nvim/issues/57