Seamless integrate phantom selections in the existing command set


#1

Let me know what you think of it.


#2

Works pretty nice!

One thing I am missing is a keybinding that does the same as <a-n> and <a-p> but without rotating the selections.

And I have a question about the keybindings:
Could you move the keybindings to a separate function, I have those keys bound to other stuff, so I will have to redefine that, which currently is a bit harder to do.


#3

You mean the insert mappings?


#4

Yes, it would be nice if the plugin could be enabled without the bindings, so that people can define those themselves


#5

It’s difficult to me because I like the semantic of the commands.


#6

@JJK96 I changed the default mappings from:

  • Alt + nAlt + )
  • Alt + pAlt + (

#7

While this solves my particular issue it is not a solution in general, because other people could still have conflicting mappings.

I propose that you make a separate command enable-mappings that would enable the default mappings; users who have conflicts could just not run that function and instead provide their own mappings.


#8

@JJK96 Done. Just use phantom-enable or phantom-enable -with-maps to do the mappings.


#9

Thanks, that should work!