From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: lisp-completion-at-point "end" position. Date: Tue, 02 Aug 2011 16:11:48 -0400 Message-ID: References: <8762my2qwu.fsf@gmail.com> <87mxfsv27k.fsf@gmail.com> <87fwljr5gy.fsf@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1312315918 4558 80.91.229.12 (2 Aug 2011 20:11:58 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 2 Aug 2011 20:11:58 +0000 (UTC) Cc: emacs-devel@gnu.org To: Thierry Volpiatto Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Aug 02 22:11:54 2011 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 1QoLJi-0003a3-J2 for ged-emacs-devel@m.gmane.org; Tue, 02 Aug 2011 22:11:54 +0200 Original-Received: from localhost ([::1]:47881 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QoLJi-00017v-3V for ged-emacs-devel@m.gmane.org; Tue, 02 Aug 2011 16:11:54 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:53458) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QoLJf-00017i-Ls for emacs-devel@gnu.org; Tue, 02 Aug 2011 16:11:52 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QoLJe-0004GK-KZ for emacs-devel@gnu.org; Tue, 02 Aug 2011 16:11:51 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.183]:31833 helo=ironport2-out.pppoe.ca) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QoLJe-0004GA-BX for emacs-devel@gnu.org; Tue, 02 Aug 2011 16:11:50 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av0EALhZOE5FxKfe/2dsb2JhbABCp2d4gUABAQQBViMFCwstBxIUGA0kh3/AAIM3gwsEn0qEMQ X-IronPort-AV: E=Sophos;i="4.67,307,1309752000"; d="scan'208";a="128460943" Original-Received: from 69-196-167-222.dsl.teksavvy.com (HELO ceviche.home) ([69.196.167.222]) by ironport2-out.pppoe.ca with ESMTP/TLS/ADH-AES256-SHA; 02 Aug 2011 16:11:49 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id DC62E660CF; Tue, 2 Aug 2011 16:11:48 -0400 (EDT) In-Reply-To: <87fwljr5gy.fsf@gmail.com> (Thierry Volpiatto's message of "Tue, 02 Aug 2011 21:14:21 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.183 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:142751 Archived-At: >>> (def(something) => doesn't complete def >>> (def! (something) => complete def >> A space should not be needed when the subsequent char is an open-paren. > At another level, not lisp-completion-at-point. No, I mean for lisp-completion-at-point. I.e. I can't reproduce the problem you show above. > My concern was lisp-completion-at-point, not the completion UI of > emacs. (i don't use it). I understand that. But completion-at-point-functions does allow point to be within the to-be-completed element (rather than only at its end) and so a UI that wants to use it needs to take this into account (it may for example elect to ignore the `end' and always use point instead). Stefan