From: Aaron Cohen <aaron@brightbytes.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 49761@debbugs.gnu.org, juri@linkov.net
Subject: bug#49761: file-cache-minibuffer-complete has become unusable for duplicate file names in MacOSX 27.x emacs
Date: Fri, 30 Jul 2021 12:12:34 -0700 [thread overview]
Message-ID: <CAJ3u-GmhmbK_OZo1+M9EKvpyhzOndLK5QyjoFof6ecQNpXuE0g@mail.gmail.com> (raw)
In-Reply-To: <838s1nr63k.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
Sorry, that remark was a response (with a smile to show benign intent) to
Juri's comment:
> ... this is the default behavior for completions that don't share a
common prefix.
... and not a response to any of your comments. No offense meant - I
really appreciate your having spent any time responding to me!!
On Fri, Jul 30, 2021 at 11:48 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Aaron Cohen <aaron@brightbytes.net>
> > Date: Fri, 30 Jul 2021 11:20:51 -0700
> > Cc: Eli Zaretskii <eliz@gnu.org>, 49761@debbugs.gnu.org
> >
> > Well, it's now the default behavior. It wasn't previously. :-)
>
> I wasn't trying to find the reason for the change in behavior, I was
> trying to help you get the behavior you want back.
>
[-- Attachment #2: Type: text/html, Size: 1941 bytes --]
next prev parent reply other threads:[~2021-07-30 19:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 19:22 bug#49761: file-cache-minibuffer-complete has become unusable for duplicate file names in MacOSX 27.x emacs Aaron Cohen
2021-07-29 17:55 ` Juri Linkov
2021-07-29 18:14 ` Eli Zaretskii
2021-07-29 18:31 ` Juri Linkov
2021-07-29 19:29 ` Eli Zaretskii
2021-07-29 19:40 ` Juri Linkov
2021-07-29 21:37 ` Aaron Cohen
2021-07-29 22:49 ` Juri Linkov
2021-07-30 5:50 ` Eli Zaretskii
2021-07-30 6:41 ` Aaron Cohen
2021-07-30 7:01 ` Eli Zaretskii
2021-07-30 17:58 ` Juri Linkov
2021-07-30 18:20 ` Aaron Cohen
2021-07-30 18:47 ` Eli Zaretskii
2021-07-30 19:12 ` Aaron Cohen [this message]
2021-08-01 8:40 ` Juri Linkov
2021-08-02 20:02 ` Aaron Cohen
2021-08-02 20:12 ` Aaron Cohen
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=CAJ3u-GmhmbK_OZo1+M9EKvpyhzOndLK5QyjoFof6ecQNpXuE0g@mail.gmail.com \
--to=aaron@brightbytes.net \
--cc=49761@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.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).