From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.devel Subject: Completions in Semantic Date: Sun, 18 Oct 2009 19:00:58 -0400 Message-ID: <87tyxwxq6t.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1255906882 20809 80.91.229.12 (18 Oct 2009 23:01:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 18 Oct 2009 23:01:22 +0000 (UTC) Cc: emacs-devel@gnu.org To: "Eric M. Ludlam" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 19 01:01:12 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MzekR-0004Cc-P5 for ged-emacs-devel@m.gmane.org; Mon, 19 Oct 2009 01:01:12 +0200 Original-Received: from localhost ([127.0.0.1]:49076 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MzekR-0004o8-BI for ged-emacs-devel@m.gmane.org; Sun, 18 Oct 2009 19:01:11 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MzekM-0004nR-GF for emacs-devel@gnu.org; Sun, 18 Oct 2009 19:01:06 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MzekG-0004kQ-3S for emacs-devel@gnu.org; Sun, 18 Oct 2009 19:01:04 -0400 Original-Received: from [199.232.76.173] (port=35970 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MzekF-0004kJ-ST for emacs-devel@gnu.org; Sun, 18 Oct 2009 19:00:59 -0400 Original-Received: from pantheon-po43.its.yale.edu ([130.132.50.104]:37323) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MzekF-0004Ry-G3 for emacs-devel@gnu.org; Sun, 18 Oct 2009 19:00:59 -0400 Original-Received: from furry (adsl-99-69-49-186.dsl.wlfrct.sbcglobal.net [99.69.49.186]) (authenticated bits=0) by pantheon-po43.its.yale.edu (8.12.11.20060308/8.12.11) with ESMTP id n9IN0wZH030468 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 18 Oct 2009 19:00:58 -0400 Original-Received: by furry (Postfix, from userid 1000) id 286F2C070; Sun, 18 Oct 2009 19:00:58 -0400 (EDT) X-YaleITSMailFilter: Version 1.2c (attachment(s) not renamed) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:116232 Archived-At: Hi Eric, The completion code implemented by the semantic/complete package appears to be quirky. For instance: emacs M-x semantic-mode RET C-x C-f ~/emacs/src/xdisp.c [visit xdisp.c in in the Emacs tree] C-c , j window[TAB] Semantic now displays a *Completions* window with the following contents: Possible completions are: window But this message is misleading, because that's definitely not the only completion. Type: _[TAB] and the *Completions* window is updated with Possible completions are: window_text_bottom_y window_box_width window_box_height On a more general note, this is one of the drawbacks to the approach taken in semantic/complete.el, i.e. trying to reimplement completion. We've painstakingly ironed out a lot of bugs in the standard Emacs completion code, and it makes no sense to redo all that for Semantic unless there's a good reason. (Not to mention inconsistency issues). In the commentary to semantic/complete.el, you write that using `all-completions' and `try-completion' isn't practical because they are too slow when there are large numbers of tags. How sure are you that that's true? Nowadays, the completions code is very flexible; for instance, you can pass `all-completions' and `try-completion' a collector function instead of a flat completion table. Can't semantic/complete.el make use of this functionality?