unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: maurooaranda@gmail.com, arstoffel@gmail.com, monnier@iro.umontreal.ca
Cc: 65089@debbugs.gnu.org
Subject: bug#65089: 30.0.50; shell-command filename completion unexpected behavior change
Date: Sat, 12 Aug 2023 09:51:06 +0300	[thread overview]
Message-ID: <834jl4g3dx.fsf@gnu.org> (raw)
In-Reply-To: <83pm41sqbs.fsf@gnu.org> (message from Eli Zaretskii on Sat, 05 Aug 2023 14:04:23 +0300)

Ping!

> Cc: 65089@debbugs.gnu.org
> Date: Sat, 05 Aug 2023 14:04:23 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> 
> > Date: Sat, 5 Aug 2023 07:46:16 -0300
> > From: Mauro Aranda <maurooaranda@gmail.com>
> > 
> > Before running emacs, setup a directory tree like this:
> > mkdir bug bug/foo-1 bug/foo-2 bug/foo-1/bar bug/foo-2/bar
> > under HOME, for simplicity.
> > 
> > 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:
> > 
> > commit a9941269683fe50673d0aa81feefb7a9d3d8a6b9
> > Author: Augusto Stoffel <arstoffel@gmail.com>
> > Date:   Thu Sep 8 11:09:42 2022 +0200
> > 
> >      pcomplete: Generate completions from --help messages
> > 
> >      * lisp/pcomplete.el (pcomplete-from-help): New function (and hash
> >      table) to get pcomplete candidates from help messages.
> >      (pcomplete-here-using-help): Helper function to define pcomplete for
> >      simple commands
> >      (pcomplete-completions-at-point): Provide annotation-function and
> >      company-docsig properties.
> >      * lisp/pcmpl-git.el: New file, provides pcomplete for Git.
> >      * lisp/pcmpl-gnu.el: Add pcomplete for awk, gpg and gdb, emacs and
> >      emacsclient.
> >      * lisp/pcmpl-linux.el: Add pcomplete for systemctl and journalctl.
> >      * lisp/pcmpl-rpm.el: Add pcomplete for dnf.
> >      * lisp/pcmpl-unix.el: Add pcomplete for sudo and most commands found
> >      in GNU Coreutils.
> >      * lisp/pcmpl-x.el: Add pcomplete for tex, pdftex, latex, pdflatex,
> >      rigrep and rclone.
> >      * test/lisp/pcomplete-tests.el (pcomplete-test-parse-gpg-help,
> >      pcomplete-test-parse-git-help): Tests for the new functions.
> > 
> > 
> > And my current workaround is to move pcomplete-completions-at-point to
> > the end in shell-dynamic-complete-functions, following what was done in
> > Bug#34330.
> 
> Adding Augusto and Stefan to the discussion.
> 
> 
> 
> 





  reply	other threads:[~2023-08-12  6:51 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 [this message]
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
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

  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=834jl4g3dx.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=65089@debbugs.gnu.org \
    --cc=arstoffel@gmail.com \
    --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 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).