provide suggested mappings

[ivanov]

Hey, this looks like a neat plugin, thanks for putting it together.

I appreciate that you don't force default mappings onto potential users, but I think it would be very useful to at least provide a sample or a suggestion of mappings (you obviously have some mapping yourself for the video, and as the author of this plugin have thought a lot more than those of us just wanting to try it out about what makes sense for a mapping).

Otherwise, it's a bit daunting to get started....

thanks!

[paradigm]

Will do. I've discussed potential recommended mappings with others and have a few ideas.

I've got another higher priority project I need to take care of first, but once that is done I'll include suggested mappings amongst other improvements to multicursor.

[caioariede]

+1 for this.

[l4u]

👍

[gut4]

+1

[MaPePeR]

👍
Also there are multiple projects with the same goal on GitHub:
https://github.com/felixr/vim-multiedit (Last-Change: 8 months ago)
forked: https://github.com/hlissner/vim-multiedit (Last-Change: 4 hours ago)
and this project: https://github.com/paradigm/vim-multicursor (Last-Change: 3 months ago)

Maybe it might be better to stick with hlissner/vim-multiedit because the other 2 projects seems to have stopped in development...

[paradigm]

I've had to take a break from developing this and a few other of my projects due to high priorities elsewhere. I had hopped to work on this over spring break (which just started for me), but I am not sure whether or not this will happen either. However, come summer I fully expect to have the time to resume work here. I do not consider this project dead or forgotten - I've taken note on every +1 for the default mappings and have a TODO elsewhere of other feature requests placed outside of github. I've simply not had the time to get back to this in the last few months.

A number of the known issues (https://github.com/paradigm/vim-multicursor/blob/master/doc/multicursor.txt#L143-L194) aren't easy to fix with the curent design of the plugin, and it will likely require a bit of re-work of how things are going under-the-hood. My next step in this project is to work out a general plan to make it feasible to clean knock out those issues before I begin actually coding - I'm more of a waterfall guy than an agile guy. Once that is done it will be much easier to knock off the rest of the TODO items, including this one.

If you'd rather go with a plugin that has been actively developed more recently than this one, you're more than welcome to. Either work on this one will resume and it will overtake it later, in which case you can switch back, or it won't, in which case I would encourage everyone to switch. However, don't make the move on the assumption that this is a dead project, because I assure you it is not.