Stefan Schimanski wrote: > I am not sure I like this fix either. This way the TAB key silently changes > its meaning when the completion becomes visible. If one waits long enough > for the inline completion to appear, suddenly the TAB in tables does not > jump to the next cell anymore...
incidentally i find it convenient, but i agree it is somewhat inconsistent ui behaviour. the lfun bindings will make the tab binding unique. i wish there was some mechanism that in case one lfun is disabled, it would try run the next lfun bound to the same key, which would let this chameleon alive :) pavel
