From: Jorgen Schaefer <forcer@forcix.cx>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: Is intellisense features integration in Emacs technically possible?
Date: Sun, 26 Jan 2014 11:15:23 +0100 [thread overview]
Message-ID: <20140126111523.4d842288@forcix.kollektiv-hamburg.de> (raw)
In-Reply-To: <8738kb1uvu.fsf@yandex.ru>
On Sun, 26 Jan 2014 01:53:09 +0200
Dmitry Gutov <dgutov@yandex.ru> wrote:
> > 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.
>
> [...]
>
> 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.
The "first" one. ;-) Basically, what you get when you hit RET in
Company, without typing anything. The delay for this can be a lot
shorter, up to "almost instantaneous", than the delay for popping up the
completion pop-up.
(Come to think of it, isn't there a way of sorting completion
results? It's one of the things I want to get auto-complete to do,
because completions from Python backends are most of the time of higher
quality than, say, dabbrev completions.)
> > 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.
I did not look much closer. The solution you provided is more or less
what auto-complete does with its init call and caching, which would
likely work slightly better than auto-complete because I have more
control over it, but well, a-c already has it implemented. Hence, I was
quite satisfied - it solves my problem, and I can not and do not expect
any more from you, you were very helpful already - but it's not what I
was hoping for.
Originally, I created the issue because I was hoping Company would be
able to fully replace auto-complete just requiring fewer hacks and
work on my part. Sadly, while working with it, I realized Company as is
does not really replace auto-complete for me. It's close, but not quite
there yet.
I want to look at Company again at some point in the future and see if
I can make a list of things I miss and maybe start working on them, but
at the moment I'm very low on time, so I pushed that down my list quite
a bit I'm afraid.
As I said in my original post, that was not intended as a request to
get all of this implemented or even as a complaint, just as a note on
what the technical hurdles for Emacs implementing IntelliSense features
actually are: Very few. The features are mostly there, and what is
missing is mainly a common API and some polishing here and there.
Regards,
Jorgen
next prev parent reply other threads:[~2014-01-26 10:15 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 2:01 Is intellisense features integration in Emacs technically possible? Jorge Araya Navarro
2014-01-21 18:59 ` Tom
2014-01-21 19:29 ` Eli Zaretskii
2014-01-21 19:58 ` Tom
2014-01-22 3:53 ` Eli Zaretskii
2014-01-22 4:36 ` Óscar Fuentes
2014-01-22 6:31 ` David Kastrup
2014-01-22 7:26 ` Stephen J. Turnbull
2014-01-22 8:13 ` David Kastrup
2014-01-22 9:33 ` Stephen J. Turnbull
2014-01-22 11:02 ` David Kastrup
2014-01-22 13:35 ` Stefan Monnier
2014-01-22 16:04 ` Eli Zaretskii
2014-01-23 8:13 ` Stephen J. Turnbull
2014-01-23 8:44 ` David Kastrup
2014-01-23 16:19 ` Eli Zaretskii
2014-01-24 2:57 ` Stephen J. Turnbull
2014-01-24 7:43 ` Eli Zaretskii
2014-01-22 8:49 ` Rüdiger Sonderfeld
2014-01-22 11:53 ` Óscar Fuentes
2014-01-22 15:56 ` Eli Zaretskii
2014-01-22 18:46 ` Stefan Monnier
2014-01-22 19:10 ` David Engster
2014-01-22 16:52 ` David Engster
2014-01-22 15:59 ` Eli Zaretskii
2014-01-22 16:41 ` David Engster
2014-01-22 17:16 ` Dmitry Gutov
2014-01-22 17:36 ` David Engster
2014-01-22 18:12 ` Óscar Fuentes
2014-01-22 18:34 ` David Engster
2014-01-21 20:03 ` Andreas Röhler
2014-01-22 3:54 ` Eli Zaretskii
2014-01-22 6:28 ` Stephen J. Turnbull
2014-01-22 16:03 ` Eli Zaretskii
2014-01-23 7:54 ` Stephen J. Turnbull
2014-01-22 17:29 ` Phillip Lord
2014-01-22 18:49 ` Jorgen Schaefer
2014-01-23 9:00 ` Andreas Röhler
2014-01-23 19:34 ` Jorgen Schaefer
2014-01-23 13:20 ` Phillip Lord
2014-01-23 15:12 ` Stefan Monnier
2014-01-23 20:56 ` Jorgen Schaefer
2014-01-23 22:13 ` Stefan Monnier
2014-01-23 22:43 ` Jorgen Schaefer
2014-01-24 1:40 ` Stefan Monnier
2014-01-24 10:25 ` Jorgen Schaefer
2014-01-24 12:46 ` Thien-Thi Nguyen
2014-01-24 13:20 ` Stefan Monnier
2014-01-25 23:42 ` Dmitry Gutov
2014-01-24 11:58 ` Phillip Lord
2014-01-25 23:53 ` Dmitry Gutov
2014-01-26 10:15 ` Jorgen Schaefer [this message]
2014-01-26 23:04 ` Dmitry Gutov
2014-01-23 2:22 ` Eric M. Ludlam
2014-01-23 13:26 ` Phillip Lord
2014-01-21 19:53 ` David Engster
2014-01-21 20:07 ` Tom
2014-01-21 20:13 ` David Engster
2014-01-21 20:24 ` Tom
2014-01-21 22:50 ` David Engster
2014-01-22 3:55 ` Eli Zaretskii
2014-01-23 9:16 ` Andreas Röhler
2014-01-23 17:17 ` Richard Stallman
[not found] <mailman.172802.1390363342.10747.emacs-devel@gnu.org>
2014-01-22 7:39 ` Jorge Araya Navarro
2014-01-22 15:39 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140126111523.4d842288@forcix.kollektiv-hamburg.de \
--to=forcer@forcix.cx \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.