I don't understand why Vim behaves differently based on different filetypes, even though it knows them all and it knows their comments characters.
for C files, it will insert a new comment when I Enter and with "double-tap" Entering again will delete the comment, which is good.
with Python it will not insert a new comment when I Enter and with "double-tap" it's "of course" the same, which is bad.
with Rust it will insert a new comment when I Enter and with "double-tap" Entering again will not delete the comment, which is bad, and when I try passing "i_CTRL+U" it will delete the comment !! so why won't "double-tap" work when almost all what it does is passing this "i_CTRL+U" when you enter on an empty comment line ?
I don't understand why Vim behaves differently based on different filetypes, even though it knows them all and it knows their comments characters.
for C files, it will insert a new comment when I Enter and with "double-tap" Entering again will delete the comment, which is good.
with Python it will not insert a new comment when I Enter and with "double-tap" it's "of course" the same, which is bad.
with Rust it will insert a new comment when I Enter and with "double-tap" Entering again will not delete the comment, which is bad, and when I try passing "i_CTRL+U" it will delete the comment !! so why won't "double-tap" work when almost all what it does is passing this "i_CTRL+U" when you enter on an empty comment line ?