From: Dmitry Gutov <dgutov@yandex.ru>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 16334@debbugs.gnu.org
Subject: bug#16334: 24.3.50; company-capf eats the first char in IELM filename completions
Date: Thu, 09 Jan 2014 10:21:23 +0400 [thread overview]
Message-ID: <52CE3FE3.4080503@yandex.ru> (raw)
In-Reply-To: <jwvob3nyx2b.fsf-monnier+emacsbugs@gnu.org>
On 08.01.2014 07:33, Stefan Monnier wrote:
>> Already done:
>> https://github.com/company-mode/company-mode/compare/b70540b5fcd062c4670dea7004453de326ff4f70...8ecec3594931ae8e2329fec4b793ad4ba392e4ef
>
> It's not in elpa yet.
It will be. Users won't get the new version until the header's bumped
anyway.
>> On the other hand, the backend is free to try all completion styles it
>
> The backends know nothing about completion styles.
Yes, but is this the best approach? I see you're taking advantage of
`completion-regexp-list' and the fact that `all-completions' is
implemented in C in `completion-pcm--all-completions', but if one would
implement a completion function using an external service, in many cases
this would mean a non-optimal amount of data to have to be transferred.
And a service's implementation of different completion styles could be
just as fast, if not faster. Omnisharp has it already, so using it
should make sense.
next prev parent reply other threads:[~2014-01-09 6:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 23:20 bug#16334: 24.3.50; company-capf eats the first char in IELM filename completions Dmitry Gutov
2014-01-04 5:00 ` Stefan Monnier
2014-01-05 2:20 ` Dmitry Gutov
2014-01-05 3:17 ` Dmitry Gutov
2014-01-05 4:53 ` Stefan Monnier
2014-01-06 5:33 ` Dmitry Gutov
2014-01-06 15:23 ` Stefan Monnier
2014-01-07 2:52 ` Dmitry Gutov
2014-01-08 3:33 ` Stefan Monnier
2014-01-09 6:21 ` Dmitry Gutov [this message]
2014-01-09 16:00 ` Stefan Monnier
2014-01-10 6:23 ` Dmitry Gutov
2014-01-10 14:58 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52CE3FE3.4080503@yandex.ru \
--to=dgutov@yandex.ru \
--cc=16334@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).