From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?ISO-8859-15?Q?Andreas_R=F6hler?= Newsgroups: gmane.emacs.devel Subject: completion--capf-wrapper Date: Wed, 18 Jan 2012 10:04:12 +0100 Message-ID: <4F168B0C.9020602@online.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1326877475 24617 80.91.229.12 (18 Jan 2012 09:04:35 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 18 Jan 2012 09:04:35 +0000 (UTC) Cc: Emacs developers To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jan 18 10:04:27 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RnRRR-0002WX-Rs for ged-emacs-devel@m.gmane.org; Wed, 18 Jan 2012 10:04:25 +0100 Original-Received: from localhost ([::1]:45641 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RnRRR-00083W-AI for ged-emacs-devel@m.gmane.org; Wed, 18 Jan 2012 04:04:25 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:58617) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RnRRK-00083O-Gp for emacs-devel@gnu.org; Wed, 18 Jan 2012 04:04:23 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RnRRJ-0001zF-KW for emacs-devel@gnu.org; Wed, 18 Jan 2012 04:04:18 -0500 Original-Received: from moutng.kundenserver.de ([212.227.17.8]:60814) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RnRRJ-0001xU-7B for emacs-devel@gnu.org; Wed, 18 Jan 2012 04:04:17 -0500 Original-Received: from [192.168.178.27] (brln-4d0c2394.pool.mediaWays.net [77.12.35.148]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0LxMeg-1SkGEW3xTW-0179n3; Wed, 18 Jan 2012 10:04:15 +0100 User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.2.24) Gecko/20111101 SUSE/3.1.16 Thunderbird/3.1.16 X-Provags-ID: V02:K0:71Y4TcyHBXWzMherf+o7TJ5ASHICFPdhqiHBvNABC80 VhH+2Xt/0w4abt8sP+TQdqYfL+fV7UbelTGfOjy1uv15AJMu0X EUOGlKfX0e2bkiP094SlkGPW8sPSDY4Yit2+F590EPbnsPMuSR q3M1RqKGQoK2qP+HYwZ3E+bed9jiUNBif3ZWJiTftmNjGenhS/ O1VL3onbI/0fF18UlFTRVfWJu7kRkq5FWSNmqMXF+EffJ1y5ve c2B+etOiX0yL27n1LIRnzl2/U3uTKgcEAx1gu7S4pxvdWMngz+ 6hBKKFQwb/fQg5WqaFLqFkC4kKS2FM850BRywU36InkSGiV/Wy JZ3hQff5yOzj4B8lLPtk= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 212.227.17.8 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:147708 Archived-At: 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