Request: Document Recommendations for missing vim-sexp mappings

[AlexChalk]

Thanks for all your work on this plugin!

I see in #49 and #53 that nvim-paredit isn't intended to be a drop-in replacement for vim-sexp. However, I suspect this is still how most users will see it, so I suggest being a bit more explicit about this in the README.

In particular, as a user I'd really appreciate a list of all the vim-sexp features that nvim-paredit doesn't include and some recommendations on how to replicate them.

I think this is a complete list of what's missing:

• sexp_flow_to_prev_close
• sexp_flow_to_next_open
• sexp_flow_to_prev_open
• sexp_flow_to_next_close
• sexp_flow_to_prev_leaf_head
• sexp_flow_to_next_leaf_head
• sexp_flow_to_prev_leaf_tail
• sexp_flow_to_next_leaf_tail
• sexp_move_to_prev_top_element
• sexp_move_to_next_top_element
• sexp_select_prev_element
• sexp_select_next_element
• sexp_indent
• sexp_indent_top
• sexp_insert_at_list_head
• sexp_insert_at_list_tail
• sexp_convolute

Let me know what you think, and thanks again.

[julienvincent]

Sorry for taking so long to reply!

Thanks for all your work on this plugin!

You are welcome :)

---

Yes fair enough I think this is probably a good idea. I don't think I'll have the time to really document ways to replicate these behaviours as they aren't really features I personally use - but I would be happy to accept contributions to that effect.

In the interim I'd be happy to include this list in docs. I plan to do some work on this plugin in the coming weeks and can address this partially then.