On Sat, Dec 28, 2013 at 9:02 AM, Stefan Monnier <monnier@iro.umontreal.ca> wrote:

Ah, right, the conflict is in the meaning of the TAB key.
There are two issues there:
1- the fact that there's no standard way to *extend* the meaning of
TAB, so autocomplete and yasnippet may both *redefine* the key instead.
2- even if the two manage to redefine TAB "at the same time", the
resulting behavior may prove too DWIMish.

This seems to be an instance of a general pattern, namely a succession of completion mechanisms desiring to be attempted based on a particular triggering event.

Does it not then follow that part of creating a more uniform completion experience ought to include direct Emacs support for that pattern? The alternative is today's hodgepodge of per-package idiosyncratic redefinition mechanisms.

/john