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: Mon, 06 Jan 2014 09:33:41 +0400 [thread overview]
Message-ID: <52CA4035.2020302@yandex.ru> (raw)
In-Reply-To: <jwvy52vowz8.fsf-monnier+emacsbugs@gnu.org>
On 05.01.2014 08:53, Stefan Monnier wrote:
>> `completion-file-name-table' is more of an exception, I think. But if
>> it was only passed the segment of STRING after the last path
>> separator, it could still look behind it in the buffer and see the
>> full path.
>
> But the completion may actually want to *change* the text before
> the boundary. E.g. completion of /u/s/d to /usr/share/doc.
In that case, "/usr/share/doc" is the completion candidate, not "doc",
right? Then, "/u/s/d" can be considered a "generalized" prefix, or the
entity to complete, in c-a-p-f terms. And during completion we delete
the latter and insert the former.
> The completion table itself does not know how to do that, but some
> completion styles do (e.g. partial-completion).
> So the completion-at-point-function needs to indicate the boundaries of
> "/u/s/d" which indicate which text can be affected by the completion,
> while `completion-boundaries' tells the lower-level completion code
> (e.g. the one in partial-completion) how to split the completion field
> into sub-fields.
To be clear, I'm not convinced that the notion of "sub-fields" is
useful. Defining limits to the text that can be affected by completion
only looks good to me from the presentation point of view: if the
candidate strings can be shorter, we can show more of them in the
*Candidates* buffer, whereas it's less useful for popup-style UIs where
the candidates are displayed vertically anyway.
IOW, if I were to add a `boundaries' action to company-backends API, it
would only be used for presentation: the popup will cut off that many
characters from the candidate strings, and it will be rendered that many
columns to the right.
And maybe do the same for suffix boundary, when/if we support that kind
of completion.
Come to think of it, though, this new action may be incompatible with
the notion of merged backends. If we have candidates that come from
backends that return the same prefix but different boundaries, there's
no way to reflect the boundaries in the popup.
next prev parent reply other threads:[~2014-01-06 5:33 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 [this message]
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
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=52CA4035.2020302@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).