Pressing <Tab> after only whitespce strips all whitespace before inputting the tab

[rabirabirara]

While investigating an earlier issue I submitted, I found what I believe is another bug (or I will look stupid if it's my own fault!).

In both gui and terminal Neovim, when pressing Tab after only whitespace characters, be they tabs or spaces, the press will erase all prior whitespace, then input the Tab. If vim detected that we were on some level of indentation before hand, then the whitespace will be stripped beyond that level of indentation.

If a single non-whitespace character comes before the input on the line, then the tab is correctly input, without any backspaces occurring.

EDIT: After further testing, it seems that pressing tab after only whitespace doesn't just strip all whitespace - if occurs in a line with no characters but whitespace, and there is a level of indentation assigned to this line, then the input will strip all whitespace, move the cursor to the indentation, and then input the Tab.

[rabirabirara]

I couldn't record my screen at the moment, but I can offer some screenshots of what happens.

I am currently heavily indented in a .jl file. I have typed the letter k. The cursor is also at that level of indentation.

I decide that I want to type another k at a previous level of indentation. I backspace somewhat and type 'k':

I press tab. For some reason, the k is moved to the current level of indentation, and the tab is then input.

If this is intended behavior, or changeable, then please do inform me! The reason why I don't believe it is is because of this oddity:

If I open a new file, test.jl, and want to input a series of tabs, I cannot input more than one Tab.

This is my cursor on line number 4, having pressed Tab once. If I press Tab any more times, the cursor does not move from that spot.

The expected behavior, as works without the plugin enabled, is for neovim to input more tab characters.

[carlobaldassi]

This was hopefully fixed in #251. Otherwise, please comment and I'll reopen.