From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, FREEMAIL_FROM,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 13806 invoked from network); 23 Jan 2023 23:15:07 -0000 Received: from mx1.math.uh.edu (129.7.128.32) by inbox.vuxu.org with ESMTPUTF8; 23 Jan 2023 23:15:07 -0000 Received: from lists1.math.uh.edu ([129.7.128.208]) by mx1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pK61o-00FIo4-IF for ml@inbox.vuxu.org; Mon, 23 Jan 2023 17:15:04 -0600 Received: from lists1.math.uh.edu ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.96) (envelope-from ) id 1pK61o-005m0M-0Z for ml@inbox.vuxu.org; Mon, 23 Jan 2023 17:15:04 -0600 Received: from mx2.math.uh.edu ([129.7.128.33]) by lists1.math.uh.edu with esmtp (Exim 4.96) (envelope-from ) id 1pK61j-005m0D-0R for ding@lists.math.uh.edu; Mon, 23 Jan 2023 17:14:59 -0600 Received: from quimby.gnus.org ([95.216.78.240]) by mx2.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pK61g-00CdSS-FF for ding@lists.math.uh.edu; Mon, 23 Jan 2023 17:14:58 -0600 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:Mime-Version:References:Message-ID:Date:Subject: From:To:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=uiqcVcHaW4rawgepEMlpx70moyPb+ny4wxcHdDX5vxI=; b=sHjgEdK2wrIAB2Z00q/P+ud/he qhoTXaJvt65Tww98+Qr+hb8SE9dJROlEt5M4emdTnSSeUEBZll+V+CvCU/p2I3N8EQMLGUoH0UyuX bUF80yRg4owCE3mWbUY9xo1Mr/yzW1zV439H5sXLGaBBKjkjqgmsNBN/hD/zm6f9I2MU=; Received: from ciao.gmane.io ([116.202.254.214]) by quimby.gnus.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pK61W-0000Hl-FQ for ding@gnus.org; Tue, 24 Jan 2023 00:14:50 +0100 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1pK61T-0002tG-3t for ding@gnus.org; Tue, 24 Jan 2023 00:14:43 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: ding@gnus.org From: Julien Cubizolles Subject: Re: completion no more working with latest HEADs (emacs and bbdb) Date: Tue, 24 Jan 2023 00:14:36 +0100 Message-ID: <87y1pszvvn.fsf@free.fr> References: <87r0y42vnh.fsf@a16n.net> <86edu3ibkp.fsf@gnu.org> <87leobgucs.fsf@a16n.net> <867czvi8d8.fsf@gnu.org> <87zgcrp63k.fsf@a16n.net> <86edu3m8fb.fsf@gnu.org> <87ilgx8uh1.fsf@free.fr> <867cxdny73.fsf@gnu.org> <86k01dtgw6.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:y7lBSwD1ruNq9CnpHYAP/Ze7PYs= List-ID: Precedence: bulk Arash Esbati writes: > Sorry for the confusion, but I have to take back my last proposal; > `eudc-capf-message-expand-name' works as expected, it is just > case-sensitive when it comes to TAB-completion. `bbdb-complete-mail' > seems to be case-insensitive. > > Julien, can you try it again and start typing names exactly as you have > them in your bbdb file and then hit TAB? I did several tests, all starting from emacs -Q. First of all by default 'completion-at-point-functions is set to (message-completion-function t). With that, TAB completes correctly incomplete names from bbdb, case insensitive, and offers several candidates: with point after "fan" in the To: field, TAB completes to "fanton", and a second TAB offers to choose between several bbdb entries with the surname fanton. In that case the completion is done by 'bbdb-complete-name not 'eudc-expand-inline. With (setq eudc-server-hotlist '(("localhost" . bbdb))) fan TAB displays "Multiple matches found: choose one", TAB then offers to choose between all the bbdb entries with "fan" either in the name, the email adress. This time, it's 'eudc-expand-inline doing. The previous attempts were without corfu. With: --8<---------------cut here---------------start------------->8--- (package-initialize) (use-package corfu) (global-corfu-mode) --8<---------------cut here---------------end--------------->8--- it gets weird. Both 'eudc-expand-inline and 'bbdb-complete-name act as they did previously but somehow TAB doesn't execute either of them, even though it's bound to 'message-tab' (according to 'describe-key) and 'message-tab does execute 'bbdb-complete-name' or 'eudc-expand-inline' as it should. I checked the value of completion-at-point-functions in message-mode, and it's set to (message-completion-function t), with no mention of eudc-capf-message-expand-name. Following your recipe, I tried: --8<---------------cut here---------------start------------->8--- (add-hook 'message-mode-hook (lambda () (setq-local completion-at-point-functions (delq 'message-completion-function completion-at-point-functions) ))) --8<---------------cut here---------------end--------------->8--- and: --8<---------------cut here---------------start------------->8--- (add-hook 'message-mode-hook (lambda () (setq-local completion-at-point-functions (append '(eudc-capf-message-expand-name) (delq 'message-completion-function completion-at-point-functions) )))) --8<---------------cut here---------------end--------------->8--- The first one sets completion-at-point-functions to t, and the second one sets it to (eudc-capf-message-expand-name t). Both fail to use a corfu completion menu when using TAB on "fan" and go back to the dialogues previously provided if I'm using (bbdb-complete-name) or (eudc-expand-inline). I hope these tests are what you had in mind and can be of use to you. Please let me know what else I can try. Thanks for your help -- Julien Cubizolles