GNU bug report logs - #24888
pcomplete/cd returns "../" before "./" and does not include empty completion in results of pcomplete-at-point

Previous Next

Full log

Message #11 received at 24888 <at> debbugs.gnu.org (full text, mbox):

From: Clément Pit--Claudel <clement.pitclaudel <at> live.com>
To: Dmitry Gutov <dgutov <at> yandex.ru>, 24888 <at> debbugs.gnu.org
Subject: Re: 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

[Message part 1 (text/plain, inline)]

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.

[signature.asc (application/pgp-signature, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.