feat(motion)!: separate flit.nvim from leap.nvim

[owittek]

This change has the benefit that only one of those plugins is active instead of both reserving keybinds

[Uzaaft]

Sensible changes. But wouldn't this be a breaking change? @owittek

[owittek]

Sensible changes. But wouldn't this be a breaking change? @owittek

Yes that was my initial thought too but considering that leap.nvim is now actually just leap.nvim I think it might be fine to not actually declare this as breaking.

[Uzaaft]

Hmm but it changes the previously expected behaviour, no?

[owittek]

I guess so, let me change it to breaking then

[luxus]

i guess we need a good commit message, dunno if its understandable that people need to add flit.nvim separately now

[owittek]

i guess we need a good commit message, dunno if its understandable that people need to add flit.nvim separately now

I would just hope for people to look into the commit if a breaking change message pops up. Not sure how to make the message clearer without writing multiple sentences

[mehalter]

I think the message is fine