From: Stefan Kangas <stefankangas@gmail.com>
To: Mauro Aranda <maurooaranda@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>,
65089@debbugs.gnu.org, Augusto Stoffel <arstoffel@gmail.com>
Subject: bug#65089: 30.0.50; shell-command filename completion unexpected behavior change
Date: Sat, 2 Sep 2023 13:07:45 -0700 [thread overview]
Message-ID: <CADwFkm=kA1bOJxTKxpMXmZNsh7_z=7kNCnzF8udu-rQMpnHfFw@mail.gmail.com> (raw)
In-Reply-To: <13457d93-12a0-bf24-22b6-0b9e4e6ca4fa@gmail.com>
Mauro Aranda <maurooaranda@gmail.com> writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
> >>> Now, with emacs -Q:
> >>> M-!
> >>> ls ~/bug/bar
> >>> Put point between "/" and "b" of "bar" and type TAB
> >>> emacs says "No match", but I expected it to offer completions,
> foo-1 and
> >>> foo-2.
> >>>
> >>> That was the behavior, at least in Emacs 28. Reverting the following
> >>> commit, returns this behavior for me:
> >
> > The patch below adds yet another heuristic to try and handle the
> > current case, but really we should rework the pcomplete API so as to
> > provide us the right info to start with.
>
> I see. Thanks for your explanation. In the meantime, I confirm that
> your patch fixes this use case.
Was this installed? I only see that the bug was left open.
next prev parent reply other threads:[~2023-09-02 20:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-05 10:46 bug#65089: 30.0.50; shell-command filename completion unexpected behavior change Mauro Aranda
2023-08-05 11:04 ` Eli Zaretskii
2023-08-12 6:51 ` Eli Zaretskii
2023-08-15 14:59 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-15 22:23 ` Mauro Aranda
2023-09-02 20:07 ` Stefan Kangas [this message]
2023-09-02 22:01 ` Mauro Aranda
2023-09-08 15:33 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-07 14:01 ` Mauro Aranda
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='CADwFkm=kA1bOJxTKxpMXmZNsh7_z=7kNCnzF8udu-rQMpnHfFw@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=65089@debbugs.gnu.org \
--cc=arstoffel@gmail.com \
--cc=eliz@gnu.org \
--cc=maurooaranda@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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.