completion--capf-wrapper

["Andreas Röhler" <andreas.roehler@online.de>]

Hi Stefan,

see completion-code has been complicating considerably since Emacs23

as for the bugs addressed in `completion--capf-wrapper' comment

   ;; FIXME: The safe/misbehave handling assumes that a given function will
   ;; always return the same kind of data, but this breaks down with 
functions
   ;; like comint-completion-at-point or mh-letter-completion-at-point, 
which
   ;; could be sometimes safe and sometimes misbehaving (and sometimes 
neither).

these bugs existed already in Emacs23 `completion-at-point'

AFAIU there is a simple solution checking for types instead of
`completion--capf-wrapper'

So far my thoughts,

Cheers,

Andreas