unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: 16334@debbugs.gnu.org
Subject: bug#16334: 24.3.50; company-capf eats the first char in IELM filename completions
Date: Sat, 04 Jan 2014 03:20:17 +0400	[thread overview]
Message-ID: <87sit4ejpq.fsf@yandex.ru> (raw)

1. Open an IELM buffer and (on Unix) type `"/' there.

2. Leave the point after `/'.

3. Type `M-x company-capf', see that all candidates have the first
character missing.

This is caused by `(comint--match-partial-filename)' matching the full
file path, including the leading slash, but
`comint-completion-file-name-table' returning base names, without any
path separators. Not sure how `completion-at-point' ignores that
problem.

Bonus round:

4. Type `/u', see the suggestion to complete it to `/ur/'.

5. Type `/usr/', then `M-x company-capf', see an error caused by some
candidates being shorter than the prefix.

In GNU Emacs 24.3.50.4 (x86_64-unknown-linux-gnu, GTK+ Version 3.8.6)
 of 2014-01-04 on axl
Bzr revision: 115859 vincentb1@users.sourceforge.net-20140103141824-juu968y9pi6r2zvv
Windowing system distributor `The X.Org Foundation', version 11.0.11403000
System Description:	Ubuntu 13.10





             reply	other threads:[~2014-01-03 23:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03 23:20 Dmitry Gutov [this message]
2014-01-04  5:00 ` bug#16334: 24.3.50; company-capf eats the first char in IELM filename completions 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
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=87sit4ejpq.fsf@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=16334@debbugs.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 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).