From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: Is intellisense features integration in Emacs technically possible? Date: Sun, 26 Jan 2014 01:53:09 +0200 Message-ID: <8738kb1uvu.fsf@yandex.ru> References: <1390269670.2888.14.camel@localhost.localdomain> <83zjmpf80o.fsf@gnu.org> <877g9shqms.fsf@newcastle.ac.uk> <20140122194930.49ba60be@forcix.kollektiv-hamburg.de> <87fvoedebx.fsf@newcastle.ac.uk> <20140123215656.30bf63b8@forcix.kollektiv-hamburg.de> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1390694003 18110 80.91.229.3 (25 Jan 2014 23:53:23 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 25 Jan 2014 23:53:23 +0000 (UTC) Cc: phillip.lord@newcastle.ac.uk, Stefan Monnier , emacs-devel@gnu.org To: Jorgen Schaefer Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 26 00:53:30 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1W7D2Y-0007by-1F for ged-emacs-devel@m.gmane.org; Sun, 26 Jan 2014 00:53:30 +0100 Original-Received: from localhost ([::1]:52943 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W7D2X-0000Mk-FI for ged-emacs-devel@m.gmane.org; Sat, 25 Jan 2014 18:53:29 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49502) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W7D2O-0000MK-MO for emacs-devel@gnu.org; Sat, 25 Jan 2014 18:53:26 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W7D2I-0002Ba-Qr for emacs-devel@gnu.org; Sat, 25 Jan 2014 18:53:20 -0500 Original-Received: from mail-ee0-x236.google.com ([2a00:1450:4013:c00::236]:62138) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W7D2I-0002BT-JL for emacs-devel@gnu.org; Sat, 25 Jan 2014 18:53:14 -0500 Original-Received: by mail-ee0-f54.google.com with SMTP id e53so1602927eek.27 for ; Sat, 25 Jan 2014 15:53:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; bh=TpQU2OeEireYdqixwl/fjiVC48iNIb6Sjm9gBpi/NzQ=; b=H+JVK89cnF257/9hMtXRjXHV3olkdpM3PZ4x6k843c8RqOiJHecye1TwnJwYHMAavS sTXJaPcT/HRtFvlTgd9OhntlCA1S9DrtEaTJQPHp+TKzMk7JNTrcBOTvXAm+qhYsj9g7 GhBuy3B4vl6ZF247uZ+knok1GQ80NKdF3gVHOz4w8825HnUN038wKuc1LrFdjn5eS4YE hj0EYKl9vWKxM5lcNDLCkq1ChPhlLzds19rKvBxeGIRTcIoQfaf8xM6bI8TtaLX2+qAf D2Ga7huKQgWnfLO09nQKajpjZ8ad9yt0tDu1ORKonbw0rJVVk0LZ16EDuXw5B1VwWuNg KdYQ== X-Received: by 10.14.127.132 with SMTP id d4mr15004211eei.66.1390693993669; Sat, 25 Jan 2014 15:53:13 -0800 (PST) Original-Received: from axl (213-173-121.netrunf.cytanet.com.cy. [213.7.173.121]) by mx.google.com with ESMTPSA id v1sm21788061eef.9.2014.01.25.15.53.12 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Sat, 25 Jan 2014 15:53:13 -0800 (PST) In-Reply-To: <20140123215656.30bf63b8@forcix.kollektiv-hamburg.de> (Jorgen Schaefer's message of "Thu, 23 Jan 2014 21:56:56 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4013:c00::236 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:169097 Archived-At: Hi Jorgen, Jorgen Schaefer writes: > Completion > ----------- > > The main topic being argued here. I'm currently using auto-complete.el, > but I hope to eventually use `completion-at-point-functions' once > company-mode is integrated. Like Stefan mentioned, you can already support Company through `completion-at-point-functions'. Company will need to be installed manually by each user, though. > Important features I haven't seen for c-a-p-f yet: Provide an overlay > of the most likely completion candidate while you type for quick > completion with TAB; add annotations to completion candidates, for > example to indicate symbol type; ability to provide documentation for a > completion candidate so that can be shown while browsing candidates. See above. But what's a "most likely completion"? When there's just one suggested completion, then yes, we show an inline overlay. Otherwise, the full list. > Oh, and support for getting completion candidates asynchronously. This > is quite tricky, as the user might have moved point in the time the > candidates were returned, and it's not always necessary to re-request > the candidates then. auto-complete.el handles this "mostly ok" using > an init function and caching the response, but has some hard to trace > problems. I remember you creating a Company issue, me writing you an example snippet, and you going away seemingly (?) satisfied. Have you had any progress using it? As long as we don't have asynchronous users, there's really not much material for me to work with to improve the API, as well as not much motivation.