From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
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 17:56:12 +0300 [thread overview]
Message-ID: <8336we0xdf.fsf@gnu.org> (raw)
In-Reply-To: <87h8kuj81s.fsf@rub.de> (message from Stephen Berman on Fri, 20 Jul 2018 16:28:15 +0200)
> 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?
next prev parent reply other threads:[~2018-07-20 14:56 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 [this message]
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=8336we0xdf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=32215@debbugs.gnu.org \
--cc=npostavs@gmail.com \
--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).