unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 9160@debbugs.gnu.org
Subject: bug#9160: 24.0.50; Emacs freezes in *shell* buffer.
Date: Tue, 06 Sep 2011 15:19:44 +0900	[thread overview]
Message-ID: <tl7liu2ur9b.fsf@m17n.org> (raw)
In-Reply-To: <jwvr546azo6.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sun, 28 Aug 2011 01:16:37 -0400)

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





  reply	other threads:[~2011-09-06  6:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-24 12:07 bug#9160: 24.0.50; Emacs freezes in *shell* buffer Kenichi Handa
2011-08-23  4:49 ` Stefan Monnier
2011-08-25  0:52   ` Kenichi Handa
2011-08-28  5:16     ` Stefan Monnier
2011-09-06  6:19       ` Kenichi Handa [this message]
2011-09-20  1:10         ` Stefan Monnier
2011-09-20  5:16           ` Kenichi Handa
2011-10-17 17:12             ` Stefan Monnier
2011-12-02 12:06               ` Kenichi Handa
2011-12-02 14:45                 ` Stefan Monnier
2011-12-04 13:41                   ` Kenichi Handa
2011-12-04 15:38                     ` 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=tl7liu2ur9b.fsf@m17n.org \
    --to=handa@m17n.org \
    --cc=9160@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).