From: Noam Postavsky <npostavs@gmail.com>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 32215@debbugs.gnu.org
Subject: bug#32215: 27.0.50; Minibuffer completion fails with /~<partial-name>
Date: Fri, 20 Jul 2018 09:58:10 -0400 [thread overview]
Message-ID: <CAM-tV--ZETHpZNE54sRGG9pASQvo1Yiy-KVwcmj=MxbcNU292A@mail.gmail.com> (raw)
In-Reply-To: <87va9ajol1.fsf@gmx.net>
On 20 July 2018 at 04:31, Stephen Berman <stephen.berman@gmx.net> wrote:
> On Thu, 19 Jul 2018 21:02:11 -0400 Noam Postavsky <npostavs@gmail.com> wrote:
>
>> Stephen Berman <stephen.berman@gmx.net> writes:
>>
>>> On Thu, 19 Jul 2018 21:19:36 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
>>>
>>>>> From: Stephen Berman <stephen.berman@gmx.net>
>>>>> Date: Thu, 19 Jul 2018 19:55:18 +0200
>>>>>
>>>>> 0. emacs -Q
>>>>> 1. C-x d / ~ TAB
>>>>> This pops up a *Completions* buffer showing directory names of all
>>>>> members of (system-users), e.g. steve/
>>>>> 2. Continuing from step 1, when I type any of 's TAB', 'st TAB', 'ste
>>>>> TAB' or 'stev TAB', Emacs responds with [No match], but 'steve TAB'
>>>>> completes to steve/
>>>>>
>>>>> The failure only happens with '/~<partial-name>', typing e.g. '~/Downl
>>>>> TAB' here completes to ~/Downloads/
>>>>
>>>> Doesn't happen here, FWIW. Strange.
>>>
>>> Strange indeed, assuming you tested on GNU/Linux or another POSIX
>>> system, since IIUC on MS-Windows system-users returns only
>>> user-real-login-name (at least it does here on Emacs 25.3 under Windows
>>> 8). I also tested on another GNU/Linux system I have with Emacs 24.3
>>> and see exactly the same behavior I described above.
>>
>> I see it on both Windows and GNU/Linux.
>
> Like Eli, I'm surprised you see it on Windows.
Oh, I skipped the TAB in step 1. With that, all of the leading text
before the ~ is removed, so there is no problem (and it indeed
completes immediately to my current user on Windows).
>
>> I notice that the after typing
>> the first letter of the user name, the leading "/" is no longer in
>> shadow face,
>
> Yes, I didn't notice that when I tested before but I do now.
Ah, so when you hit TAB, the leading "/" is not removed?
next prev parent reply other threads:[~2018-07-20 13:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 17:55 bug#32215: 27.0.50; Minibuffer completion fails with /~<partial-name> Stephen Berman
2018-07-19 18:19 ` Eli Zaretskii
2018-07-19 20:11 ` Stephen Berman
2018-07-20 1:02 ` Noam Postavsky
2018-07-20 6:40 ` Eli Zaretskii
2018-07-20 8:31 ` Stephen Berman
2018-07-20 13:58 ` Noam Postavsky [this message]
2018-07-20 14:28 ` Stephen Berman
2018-07-20 14:56 ` Eli Zaretskii
2018-07-20 15:06 ` Eli Zaretskii
2018-07-20 15:08 ` Stephen Berman
2018-07-20 17:22 ` Eli Zaretskii
2018-07-20 17:30 ` Stephen Berman
2018-07-20 19:03 ` Eli Zaretskii
2018-07-20 21:46 ` Stephen Berman
2018-07-20 6:39 ` Eli Zaretskii
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='CAM-tV--ZETHpZNE54sRGG9pASQvo1Yiy-KVwcmj=MxbcNU292A@mail.gmail.com' \
--to=npostavs@gmail.com \
--cc=32215@debbugs.gnu.org \
--cc=stephen.berman@gmx.net \
/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).