You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
flit.nvim enchances the ft command by labeling mutiple matches to jump to. But when I'm recording a macro, if I use f or t command in the macro, sometimes it will mess up the macro behavior and jump to somewhere i didn't intend to. For example, I records a macro of f,h, meaning find next , and move one character left, then i apply this macro to multiple lines. But if these is a label h existing after f, the h will jump to it, making the macro totally unpredictable.
The text was updated successfully, but these errors were encountered:
I guess you can add autocommands to unmap f/t on RecordingEnter and re-init flit on RecordingLeave. (Or simply set multiline = false.) But that only solves the recording part. See also ggandor/lightspeed.nvim#14.
A less than perfect solution is to include turning flit on/off in the recording itself :)
flit.nvim
enchances thef
t
command by labeling mutiple matches to jump to. But when I'm recording a macro, if I usef
ort
command in the macro, sometimes it will mess up the macro behavior and jump to somewhere i didn't intend to. For example, I records a macro off,h
, meaning find next,
and move one character left, then i apply this macro to multiple lines. But if these is a labelh
existing afterf
, theh
will jump to it, making the macro totally unpredictable.The text was updated successfully, but these errors were encountered: