From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Dmitry Gutov <dgutov@yandex.ru>
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 11:00:10 -0500 [thread overview]
Message-ID: <jwv8uupf95g.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <52CE3FE3.4080503@yandex.ru> (Dmitry Gutov's message of "Thu, 09 Jan 2014 10:21:23 +0400")
>>> 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.
That's true. That function could make use of completion-regexp-list,
but maybe it can't support full regexps (and even if it can, it then
requires translating Emacs regexps to the format used by the external
tool).
This is a limitation inherited from the "original" completion
infrastructure. We could easily introduce a replacement for
completion-regexp-list which specifies a "pattern" (in a format to be
defined).
This said, even if the external service can't just take an Emacs regexp,
the completion function can parse the regexp from completion-regexp-list
and turn it into a different/simpler pattern.
> And a service's implementation of different completion styles could be just
> as fast, if not faster.
Of course, it's only interesting if it's faster, otherwise, why bother?
Stefan
next prev parent reply other threads:[~2014-01-09 16:00 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
2014-01-09 16:00 ` Stefan Monnier [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv8uupf95g.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=16334@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
/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.