On 09/06/2007 05:35:33 PM, Enrico Tröger wrote:
On Wed, 5 Sep 2007 17:12:20 -0600, Steve steve@trinidadgraphics.com wrote:
On Wed, 5 Sep 2007 21:52:36 +0200 Enrico Tröger enrico.troeger@uvena.de wrote:
On Tue, 4 Sep 2007 23:12:32 -0600, Steve steve@trinidadgraphics.com wrote:
Autocompletion.conf expansions don't work if there is text on the line after the expansion point. Is there a way to fix this? They work fine on empty lines or at the end of a line. I'm
using
build 1851.
This is a feature not a bug. We discussed this partly on this
list
[1]. IMO it is better to not auto complete if the cursor is not
at
the end of a line.
Out of curiosity, why?
Because it may confuse too much when accidentally hitting [Tab] (or whatever the auto completion is bound to) and is probably very unexpected.
When I first added this behaviour, it was when the default autocompletion was triggered just by typing space. So I added it so the autocompletion wasn't triggered when e.g. typing 'if' at the start of a line that already had text on it.
Now I can't really think of a situation where this is necessary. Are there any real situations where this is a problem?
Also, if it is useful, maybe we should add a (possibly hidden) preference to disable it.
Regards, Nick