* completion--capf-wrapper
@ 2012-01-18 9:04 Andreas Röhler
0 siblings, 0 replies; only message in thread
From: Andreas Röhler @ 2012-01-18 9:04 UTC (permalink / raw)
To: Stefan Monnier; +Cc: Emacs developers
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2012-01-18 9:04 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-01-18 9:04 completion--capf-wrapper Andreas Röhler
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.