[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#32215: 27.0.50; Minibuffer completion fails with /~<partial-name>
From: |
Stephen Berman |
Subject: |
bug#32215: 27.0.50; Minibuffer completion fails with /~<partial-name> |
Date: |
Fri, 20 Jul 2018 17:08:39 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
On Fri, 20 Jul 2018 17:56:12 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Stephen Berman <stephen.berman@gmx.net>
>> Cc: Eli Zaretskii <eliz@gnu.org>, 32215@debbugs.gnu.org
>> Date: Fri, 20 Jul 2018 16:28:15 +0200
>>
>> Nothing is removed. To be explicit, when I start with -Q and type 'C-x
>> d', the minibuffer displays this:
>>
>> Dired (directory): ~/
>>
>> with point after '/'. When I now type '/', the face of '~/' changes to
>> shadow, and when I then type '~', the face of the second '/' also
>> changes to shadow. When I now type TAB, the minibuffer looks like this:
>>
>> Dired (directory): ~//~
>>
>> with '~//' in shadow face, and a *Completions* buffer pops up and shows
>> the directory names of all members of (system-users). When I now type
>> 's TAB', the face of the second '/' changes from shadow to default
>> (black), '[No match]' appears after the cursor and the *Completions*
>> buffer disappears. I.e., the minibuffer looks like this on hitting TAB:
>>
>> Dired (directory): ~//~s█[No match]
>>
>> with '~/' in shadow face and '/~s' in default face, and after a couple
>> of seconds, '[No match]' disappears, leaving the rest.
>
> Ah, I think I understand why I couldn't reproduce the problem: it
> seems to only happen if default-directory is "~/" before starting the
> recipe. If it is something else, the problem doesn't happen. Can you
> confirm?
I'm afraid not:
0. emacs -Q
1. M-x cd RET /tmp/ RET
2. C-x d /~s TAB
results in this minibuffer display:
Dired (directory): /tmp//~s█[No match]
with '/tmp/' in shadow face and '/~s' in default face. Same thing with
any other value of default-directory I've tried.
Steve Berman
- bug#32215: 27.0.50; Minibuffer completion fails with /~<partial-name>, Stephen Berman, 2018/07/19
- bug#32215: 27.0.50; Minibuffer completion fails with /~<partial-name>, Eli Zaretskii, 2018/07/19
- bug#32215: 27.0.50; Minibuffer completion fails with /~<partial-name>, Stephen Berman, 2018/07/19
- bug#32215: 27.0.50; Minibuffer completion fails with /~<partial-name>, Noam Postavsky, 2018/07/19
- bug#32215: 27.0.50; Minibuffer completion fails with /~<partial-name>, Eli Zaretskii, 2018/07/20
- bug#32215: 27.0.50; Minibuffer completion fails with /~<partial-name>, Stephen Berman, 2018/07/20
- bug#32215: 27.0.50; Minibuffer completion fails with /~<partial-name>, Noam Postavsky, 2018/07/20
- bug#32215: 27.0.50; Minibuffer completion fails with /~<partial-name>, Stephen Berman, 2018/07/20
- bug#32215: 27.0.50; Minibuffer completion fails with /~<partial-name>, Eli Zaretskii, 2018/07/20
- bug#32215: 27.0.50; Minibuffer completion fails with /~<partial-name>, Eli Zaretskii, 2018/07/20
- bug#32215: 27.0.50; Minibuffer completion fails with /~<partial-name>,
Stephen Berman <=
- bug#32215: 27.0.50; Minibuffer completion fails with /~<partial-name>, Eli Zaretskii, 2018/07/20
- bug#32215: 27.0.50; Minibuffer completion fails with /~<partial-name>, Stephen Berman, 2018/07/20
- bug#32215: 27.0.50; Minibuffer completion fails with /~<partial-name>, Eli Zaretskii, 2018/07/20
- bug#32215: 27.0.50; Minibuffer completion fails with /~<partial-name>, Stephen Berman, 2018/07/20
- bug#32215: 27.0.50; Minibuffer completion fails with /~<partial-name>, Eli Zaretskii, 2018/07/20