all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Manuel Giraud via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Visuwesh <visuweshm@gmail.com>
Cc: 74944@debbugs.gnu.org
Subject: bug#74944: 31.0.50; Double TAB does not pop up *Completions* buffer when completing filename with dashes
Date: Sat, 21 Dec 2024 13:31:04 +0100	[thread overview]
Message-ID: <87cyhlusjb.fsf@ledu-giraud.fr> (raw)
In-Reply-To: <87msgtyx32.fsf@gmail.com> (Visuwesh's message of "Wed, 18 Dec 2024 18:20:09 +0530")

Visuwesh <visuweshm@gmail.com> writes:

> When completing filenames with dashes in them inside a shell-buffer,
> double TAB does not pop open the *Completions* buffer because it
> conflicts with argument completion.  To reproduce,
>
>     1. cd /tmp
>     2. mkdir test; cd test
>     3. touch blah_blah-pos-1.xyz; touch wowow-pos-1.xyz
>     4. Go to this directory in a shell buffer
>     5. Type rm pos.xyz TAB
>     6. Observe how it completes to `rm -pos-1.xyz'
>     7. Press TAB again and observe *Completions* buffer not popping up

Hi Visuwesh,

I can reproduce this.  FWIW, by instrumenting
`shell-filename-completion' with edebug, I can see that there is a
correct *Completions* buffer at some point but it "disappears" later.
I'll try to investigate it further.
-- 
Manuel Giraud





  reply	other threads:[~2024-12-21 12:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-18 12:50 bug#74944: 31.0.50; Double TAB does not pop up *Completions* buffer when completing filename with dashes Visuwesh
2024-12-21 12:31 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-12-22 11:45   ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-26 13:11     ` Visuwesh

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=87cyhlusjb.fsf@ledu-giraud.fr \
    --to=bug-gnu-emacs@gnu.org \
    --cc=74944@debbugs.gnu.org \
    --cc=manuel@ledu-giraud.fr \
    --cc=visuweshm@gmail.com \
    /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.