Pressing <tab> at the end of the line has no effect.

[aplteam]

It should jump to the next tab stop like the ODE.

[jayfoad]

Sounds like #194, which was fixed.

[e9gille]

I believe the regression is caused by the introduction of shell style autocomplete. Tab key was extended to trigger suggestions when pressed (single time in classic mode and twice in shell style) and text is present to the left.

I think what should happen is that a soft tab is inserted when there are no completion items. In that case, a single tab would be sufficient in classic mode and two tabs in shell mode, both inserting a single soft tab.

[e9gille]

Correction, a single tab should be sufficient in both cases as we would know if there are completion items and could insert soft tabs immediately.

[JohnScholes]

... a single tab should be sufficient in both cases as we would know if there are completion items and could insert soft tabs immediately.

I use shell-style autocomplete. The only downside of this would be having to back up over the blanks inserted by the soft tab if an expected word doesn't exist. At present, hitting tab twice confirms this without moving the input cursor.