From: Stephen Berman <stephen.berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 32215@debbugs.gnu.org, npostavs@gmail.com
Subject: bug#32215: 27.0.50; Minibuffer completion fails with /~<partial-name>
Date: Fri, 20 Jul 2018 19:30:52 +0200 [thread overview]
Message-ID: <878t65ke5v.fsf@rub.de> (raw)
In-Reply-To: <83y3e5zuss.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 20 Jul 2018 20:22:27 +0300")
On Fri, 20 Jul 2018 20:22:27 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Stephen Berman <stephen.berman@gmx.net>
>> Cc: npostavs@gmail.com, 32215@debbugs.gnu.org
>> Date: Fri, 20 Jul 2018 17:08:39 +0200
>>
>> > 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]
>
> Try a subdirectory of your home directory.
Perhaps I'm misunderstanding what you're suggesting, but with the
following I still get the same behavior:
0. emacs -Q
1. M-x cd RET ~/Downloads/ RET
2. C-x d /~s TAB
results in this minibuffer display:
Dired (directory): ~/Downloads//~s█[No match]
Steve Berman
next prev parent reply other threads:[~2018-07-20 17:30 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878t65ke5v.fsf@rub.de \
--to=stephen.berman@gmx.net \
--cc=32215@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=npostavs@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.