From: Michael Wu <john.michael.wu@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 36435@debbugs.gnu.org
Subject: bug#36435: ido mode C-x C-f not showing regular files in special instances
Date: Mon, 15 Jul 2019 22:58:09 -0400 [thread overview]
Message-ID: <CABuWmYOSt6iFpQDXVeDLv2Tqs8PjbZJmv_gmjqF-UMvU3cgmuQ@mail.gmail.com> (raw)
In-Reply-To: <877e8s169v.fsf@mouse.gnus.org>
[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]
Uhh sure. Here it is.
#!/bin/bash
mkdir -p d1/d1 d1/d2 d2/d1 d2/d2 d1/d1/d1 d1/d1/d2 d2/d1/da d2/d1/db
touch d1/d1/{a..c} d2/d1/{1..3}
Were you able to reproduce the issue?
On Mon, Jul 8, 2019 at 7:00 PM Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Michael Wu <john.michael.wu@gmail.com> writes:
>
> > Emacs 26.2.
> >
> > I do not know exactly the set of cases this bug appears, but here is a
> way (albeit
> > specific) that works every time for me.
> >
> > I have the following directory hierarchy:
> >
> > .
> > ├── d1
> > │ ├── d1
> > │ │ ├── a
> > │ │ ├── b
> > │ │ ├── c
> > │ │ ├── d1
> > │ │ └── d2
> > │ └── d2
> > └── d2
> > ├── d1
> > │ ├── 1
> > │ ├── 2
> > │ ├── 3
> > │ ├── da
> > │ └── db
> > └── d2
> >
> > The d's are directories. If I make d1/d1 my working directory, and then
> do
> > (exactly this sequence of keys)
>
> Do you have a shell script that can create this hierarchy so that it's
> easier to reproduce? :-)
>
> > C-x C-f, M-b, M-b, C-k, 2<TAB>, 1<TAB>
> >
> > I am shown only `da` and `db`, and not the files `1`, `2`, or `3`.
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
>
[-- Attachment #2: Type: text/html, Size: 2136 bytes --]
next prev parent reply other threads:[~2019-07-16 2:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-29 15:35 bug#36435: ido mode C-x C-f not showing regular files in special instances Michael Wu
2019-07-08 23:00 ` Lars Ingebrigtsen
2019-07-16 2:58 ` Michael Wu [this message]
2019-07-18 12:25 ` Lars Ingebrigtsen
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=CABuWmYOSt6iFpQDXVeDLv2Tqs8PjbZJmv_gmjqF-UMvU3cgmuQ@mail.gmail.com \
--to=john.michael.wu@gmail.com \
--cc=36435@debbugs.gnu.org \
--cc=JohnMichaelWu@gmail.com \
--cc=larsi@gnus.org \
/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.