Operator-pending mode for text objects in Readme
Text object definition should be using Operator-pending mode (omap) rather than xmap.
Also prefixed Update seems to break motions (e.g. diz or >iz didn't work, but does after removing prefix as in this PR)
Thank you for the suggestion and agreed that the operator-pending mappings are missing. Their definition given here should update the folds first, like the visual-mode mappings. It is missing as my naive tries did not succeed.
Indeed, I've tried it including the update fold first (prefixing :<c-u>FastFoldUpdate<cr><esc>), but it didn't work for some reason. Excluding it does work as in the PR (have you tried it?), maybe this is not optimal, but could good enough to include it.
At the least the heading should be changed since xmap doesn't really Create a fold text object (omap does though).
Okay, these operator-maps can be readded (on top of the visual-mode mappings), but they would be more pertinent if they achieved updating the folds before.