Subject: Re: bug#1207: 23.0.60; read-shell-command does not support Windows ".." quoting of file names with embedded white space

From: Juanma Barranquero <[email-masked]>
Date: Wed, 6 Jul 2011 19:12:14 +0200

On Sun, Oct 19, 2008 at 18:29, Eli Zaretskii <[email-masked]> wrote:

> On MS-Windows:
>
>  emacs -Q
>  M-! "C:/Progra TAB
>
> This correctly completes to `"c:/Program Files/'.  However, the next
> TAB fails with `[No completions of Files/]', which is an evidence that
> `read-shell-command' does not pay attention to the fact that the
> command begins with a quote character.
>
> If I type the closing quote character manually, then
>
>  "C:/Program Files/" TAB
>
> pops up a *Completions* buffer with files in my home directory (???),
> which is again incorrect.

Not only still fails for me, I can even make it hang Emacs.

M-! "C:/Progra <TAB>   => "[no match]"

M-! C:/Progra <TAB>    =>  c:/Program
<TAB>                  => offers possible completions: "Program Files",
                          "Program Files (x86)" and "ProgramData"
<SPACE> <TAB>          => no answer, not even [no match]
<BACKSPACE>
\ <SPACE> <TAB>        => "[no match]"
<TAB>                  => Emacs hangs

Sometimes it needs a few more <TAB>, or <BACKSPACE> <SPACE> <TAB>
again, but it hangs every time.

After interruping it, the backtrace is

(gdb) bt
#0  0x770e01c4 in ntdll!LdrFindResource_U () from C:\Windows\system32\ntdll.dll

Lisp Backtrace:
"pcomplete-parse-comint-arguments" (0x88d4b8)
"pcomplete-parse-arguments" (0x88d724)
0x3410480 There is no member named size.

    Juanma