How do you remove the extra space at the end of a tab completion? I just recently downloaded 4.28 and I don't have the space after word checked in the tab completion. If I do check the space after word in tab completion, it adds a second space at the end and unchecking it doesn't fix the problem.
Extra space appears after you tab-complete
Posted by Syros on Sat 21 Jun 2008 06:44 AM — 5 posts, 17,866 views.
Well now I feel like an idiot. I added the extra space when there was already that option.
Funny I didn't notice it when adding it. You can't remove it, just have to wait for the next version, sorry.
Funny I didn't notice it when adding it. You can't remove it, just have to wait for the next version, sorry.
No irony or other negative stuff intended, but this thread made my day.
Why? It's rare to see developers so zealous with adding stuff to please their customers (or I suppose userbase is a better word these days) that they add an already-existing feature a second time, except without the actual ability to turn the second one off. :D
Well done, Nick. :)
Why? It's rare to see developers so zealous with adding stuff to please their customers (or I suppose userbase is a better word these days) that they add an already-existing feature a second time, except without the actual ability to turn the second one off. :D
Well done, Nick. :)
Yes it *was* kind of funny. Thanks for the compliments Worstje.
The humorous part was that the program has so many features that even the developer forgot what they were. ;)
That is why I try to document everything as I go, but I obviously missed that one. It was partly because adding the extra space, which was already there, was a bit separated by other code from where I put the new bit (basically because plugins can get at the tab-completion).
The humorous part was that the program has so many features that even the developer forgot what they were. ;)
That is why I try to document everything as I go, but I obviously missed that one. It was partly because adding the extra space, which was already there, was a bit separated by other code from where I put the new bit (basically because plugins can get at the tab-completion).
Heh, that totally explains it. I can imagine this being a typical case of the forest preventing you from seeing the trees. :)