From: "Clément Pit--Claudel" <clement.pitclaudel@live.com>
To: Dmitry Gutov <dgutov@yandex.ru>, 24888@debbugs.gnu.org
Subject: bug#24888: pcomplete/cd returns "../" before "./" and does not include empty completion in results of pcomplete-at-point
Date: Sun, 6 Nov 2016 20:04:53 -0500 [thread overview]
Message-ID: <3629cbb6-abe6-c544-c9a1-ede630a73bba@live.com> (raw)
In-Reply-To: <74e70af1-2db5-0dbc-c3e4-6b575cd9bc93@yandex.ru>
[-- Attachment #1.1: Type: text/plain, Size: 868 bytes --]
On 2016-11-06 19:15, Dmitry Gutov wrote:
> Does it? It seems to go through comint-completion-at-point here,
> which tries comint-c-a-p-replace-by-expanded-history and
> comint-filename-completion, neither of which reference pcomplete.
Putting a breakpoint in that function and running completion doesn't trigger it for me :)
I see this:
comint-dynamic-complete-functions is a variable defined in ‘comint.el’. Its
value is (comint-c-a-p-replace-by-expanded-history
shell-environment-variable-completion shell-command-completion
shell-c-a-p-replace-by-expanded-directory pcomplete-completions-at-point
shell-filename-completion comint-filename-completion)
pcomplete-completions-at-point comes first, and is missing the "" completion.
There may be a similar problem with comint-filename-completion, of course.
Clément.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-11-07 1:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-05 23:53 bug#24888: pcomplete/cd returns "../" before "./" and does not include empty completion in results of pcomplete-at-point Clément Pit--Claudel
2016-11-07 0:15 ` Dmitry Gutov
2016-11-07 1:04 ` Clément Pit--Claudel [this message]
2016-11-07 13:48 ` Dmitry Gutov
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=3629cbb6-abe6-c544-c9a1-ede630a73bba@live.com \
--to=clement.pitclaudel@live.com \
--cc=24888@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.