bug#9160: 24.0.50; Emacs freezes in *shell* buffer.

[Kenichi Handa]

In article <jwvr546azo6.fsf-monnier+emacs@gnu.org>, Stefan Monnier 
<monnier@iro.umontreal.ca> writes:

> > Thank you I confirmed that the above test case now works.
> > But, found another bug.  If I use `rm' command instead of
> > `ls':
> >   % rm 0\ TAB
> > the completion doesn't work and I just see a message "No
> > match".

> If there's not space after the backslash, then that's a bug that's
> already in Emacs-23, and I don't know yet how to fix it.
> When there is a space after the backslash, we indeed have a bug and
> I think I've fixed it with the patch below.

I confirmed that that above test case is fixed now.  But, I
found several other bugs related completions.  All the
following testcases are with the latest trunk Emacs with -Q
argument, and they don't happen with Emacs 23.3.

(1) SPC not escaped in *Completions* buffer
% mkdir tmp
% cd tmp
% touch '0 a' '0-a'
% rm 0<tab>

Now the the *Completions* buffer is:
<...>
Possible completions are:
0 a
0-a

Note that SPC is not escapsed in '0 a'.  So, when I click
it, *shell* buffer becomes this:
% rm 0 a

This happens with 'ls' command too.

(2) The second arg to rm command is not completed.
% mkdir tmp
% cd tmp
% touch abc def
% rm a<tab>
% rm abc d<tab>

Now just "No match" is shown instead of "d" completed to
"def".  This DOES NOT happen with 'ls' command.

(3) Error in post-command-hook for *.tar.gz file.
% mkdir tmp
% cd tmp
% echo abc > abc
% echo def > def
% tar cfz temp.tar.gz abc def
% tar tfz temp<tab>

Now the command line is correctly completed to:
% tar tfz temp.tar.gz 

But, this error is signaled:

Error in post-command-hook (completion-in-region--postch): (wrong-type-argument 
listp [tar-header #<marker at 513 in  *tar-data temp.tar.gz*> abc 436 8308 8308 
4 (20069 47563) 4380 nil  ustar  handa handa 0 0 nil])

---
Kenichi Handa
handa@m17n.org