bug#1285: 23.0.60; minibuffer-complete and `C-x d'

bug#1285: 23.0.60; minibuffer-complete and `C-x d'

[Stephen Berman]

In GNU Emacs 23.0.60.12 (i686-pc-linux-gnu, GTK+ Version 2.12.9)
 of 2008-10-25 on escher

When I type `C-x d <something> TAB', where `<something>' is any sequence
of characters, then if `<something>' can complete to more than one
directory name, then the *Completions* buffer displays only those
directory names, but no non-directory file names.  But if `<something>'
can complete to a non-directory file name, then it does.  For example,
on my system `C-x d /usr/lib/libv TAB' completes to '/usr/lib/libvisual'
and after a second TAB the *Completions* buffer displays:

Possible completions are:
libvisual-0.4/
libvisual/

But `C-x d /usr/lib/libvisual-0.4. TAB' completes to '/usr/lib/libvisual-0.4.so.0'
and after a second TAB the *Completions* buffer displays:

Possible completions are:
libvisual-0.4.so.0
libvisual-0.4.so.0.0.0

Typing `C-x C-f /usr/lib/libvis TAB' completes to '/usr/lib/libvisual'
and after a second TAB the *Completions* buffer displays:

Possible completions are:
libvisual-0.4.so.0		   libvisual-0.4.so.0.0.0
libvisual-0.4/			   libvisual/

(In Emacs 22.2, `C-x d [or: C-x C-f] /usr/lib/libvis TAB' does just the
latter.)

This is with -Q, and I get the same behavior with completion-styles set
to any of `basic', `emacs21', emacs22', or `partial-completion'.

bug#1285: marked as done (23.0.60; minibuffer-complete and `C-x d')

[Emacs bug Tracking System]

[-- Attachment #1: Type: text/plain, Size: 842 bytes --]


Your message dated Sat, 08 Nov 2008 09:25:33 -0500
with message-id <87od0qxpk2.fsf@cyd.mit.edu>
and subject line Re: 23.0.60; minibuffer-complete and `C-x d'
has caused the Emacs bug report #1285,
regarding 23.0.60; minibuffer-complete and `C-x d'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact don@donarmstrong.com
immediately.)


-- 
1285: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=1285
Emacs Bug Tracking System
Contact don@donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 3427 bytes --]

From: Stephen Berman <stephen.berman@gmx.net>
To: emacs-pretest-bug@gnu.org
Subject: 23.0.60; minibuffer-complete and `C-x d'
Date: Fri, 31 Oct 2008 16:16:07 +0100
Message-ID: <87k5bo7q2w.fsf@escher.local.home>

In GNU Emacs 23.0.60.12 (i686-pc-linux-gnu, GTK+ Version 2.12.9)
 of 2008-10-25 on escher

When I type `C-x d <something> TAB', where `<something>' is any sequence
of characters, then if `<something>' can complete to more than one
directory name, then the *Completions* buffer displays only those
directory names, but no non-directory file names.  But if `<something>'
can complete to a non-directory file name, then it does.  For example,
on my system `C-x d /usr/lib/libv TAB' completes to '/usr/lib/libvisual'
and after a second TAB the *Completions* buffer displays:

Possible completions are:
libvisual-0.4/
libvisual/

But `C-x d /usr/lib/libvisual-0.4. TAB' completes to '/usr/lib/libvisual-0.4.so.0'
and after a second TAB the *Completions* buffer displays:

Possible completions are:
libvisual-0.4.so.0
libvisual-0.4.so.0.0.0

Typing `C-x C-f /usr/lib/libvis TAB' completes to '/usr/lib/libvisual'
and after a second TAB the *Completions* buffer displays:

Possible completions are:
libvisual-0.4.so.0		   libvisual-0.4.so.0.0.0
libvisual-0.4/			   libvisual/

(In Emacs 22.2, `C-x d [or: C-x C-f] /usr/lib/libvis TAB' does just the
latter.)

This is with -Q, and I get the same behavior with completion-styles set
to any of `basic', `emacs21', emacs22', or `partial-completion'.





[-- Attachment #3: Type: message/rfc822, Size: 1666 bytes --]

From: Chong Yidong <cyd@stupidchicken.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 1285-done@emacsbugs.donarmstrong.com
Subject: Re: 23.0.60; minibuffer-complete and `C-x d'
Date: Sat, 08 Nov 2008 09:25:33 -0500
Message-ID: <87od0qxpk2.fsf@cyd.mit.edu>

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> How bout reverting to the old version of dired-read-dir-and-switches
>> then?  (We can keep the new version commented out, so that someone can
>> come back to try and get it working properly later.)
>
> Sure,

Done.

bug#1285: 23.0.60; minibuffer-complete and `C-x d'

[Chong Yidong]

> When I type `C-x d <something> TAB', where `<something>' is any sequence
> of characters, then if `<something>' can complete to more than one
> directory name, then the *Completions* buffer displays only those
> directory names, but no non-directory file names.  But if `<something>'
> can complete to a non-directory file name, then it does.

I think the new completion behavior for C-x d is well-intentioned, but
too complicated.  Hence the user confusion reported here.  Stefan: WDYT
about switching back to the old version of dired-read-dir-and-switches?

bug#1285: 23.0.60; minibuffer-complete and `C-x d'

[Stefan Monnier]

>> When I type `C-x d <something> TAB', where `<something>' is any sequence
>> of characters, then if `<something>' can complete to more than one
>> directory name, then the *Completions* buffer displays only those
>> directory names, but no non-directory file names.  But if `<something>'
>> can complete to a non-directory file name, then it does.

> I think the new completion behavior for C-x d is well-intentioned, but
> too complicated.  Hence the user confusion reported here.  Stefan: WDYT
> about switching back to the old version of dired-read-dir-and-switches?

How 'bout keeping the completion behavior as is, but changing the
*Completions* buffer to list all files?


        Stefan

bug#1285: 23.0.60; minibuffer-complete and `C-x d'

[Chong Yidong]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>> When I type `C-x d <something> TAB', where `<something>' is any sequence
>>> of characters, then if `<something>' can complete to more than one
>>> directory name, then the *Completions* buffer displays only those
>>> directory names, but no non-directory file names.  But if `<something>'
>>> can complete to a non-directory file name, then it does.
>
>> I think the new completion behavior for C-x d is well-intentioned, but
>> too complicated.  Hence the user confusion reported here.  Stefan: WDYT
>> about switching back to the old version of dired-read-dir-and-switches?
>
> How 'bout keeping the completion behavior as is, but changing the
> *Completions* buffer to list all files?

How do we do that?

bug#1285: 23.0.60; minibuffer-complete and `C-x d'

[Stefan Monnier]

>>>> When I type `C-x d <something> TAB', where `<something>' is any sequence
>>>> of characters, then if `<something>' can complete to more than one
>>>> directory name, then the *Completions* buffer displays only those
>>>> directory names, but no non-directory file names.  But if `<something>'
>>>> can complete to a non-directory file name, then it does.
>> 
>>> I think the new completion behavior for C-x d is well-intentioned, but
>>> too complicated.  Hence the user confusion reported here.  Stefan: WDYT
>>> about switching back to the old version of dired-read-dir-and-switches?
>> 
>> How 'bout keeping the completion behavior as is, but changing the
>> *Completions* buffer to list all files?

> How do we do that?

Good question,


        Stefan

bug#1285: 23.0.60; minibuffer-complete and `C-x d'

[Chong Yidong]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>>> I think the new completion behavior for C-x d is well-intentioned, but
>>>> too complicated.  Hence the user confusion reported here.  Stefan: WDYT
>>>> about switching back to the old version of dired-read-dir-and-switches?
>>> 
>>> How 'bout keeping the completion behavior as is, but changing the
>>> *Completions* buffer to list all files?
>
>> How do we do that?
>
> Good question

How bout reverting to the old version of dired-read-dir-and-switches
then?  (We can keep the new version commented out, so that someone can
come back to try and get it working properly later.)

bug#1285: 23.0.60; minibuffer-complete and `C-x d'

[Stefan Monnier]

>>>>> I think the new completion behavior for C-x d is well-intentioned, but
>>>>> too complicated.  Hence the user confusion reported here.  Stefan: WDYT
>>>>> about switching back to the old version of dired-read-dir-and-switches?
>>>> 
>>>> How 'bout keeping the completion behavior as is, but changing the
>>>> *Completions* buffer to list all files?
>> 
>>> How do we do that?
>> 
>> Good question

> How bout reverting to the old version of dired-read-dir-and-switches
> then?  (We can keep the new version commented out, so that someone can
> come back to try and get it working properly later.)

Sure,


        Stefan