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: Tue, 07 Jan 2025 16:01:32 +0100 [thread overview]
Message-ID: <87ikqqwtv7.fsf@ledu-giraud.fr> (raw)
In-Reply-To: <87wmfmd1x4.fsf@gmail.com> (Visuwesh's message of "Thu, 26 Dec 2024 18:41:35 +0530")
Visuwesh <visuweshm@gmail.com> writes:
[...]
> The second call which moves the before the first '-' makes sense to me
> since to complete further one, one has to insert text before that
> character. This happens elsewhere too so I am not exactly surprised.
> However, I think this is where the capf gets stuck since Emacs thinks it
> has to complete an option / a flag and the completion engine stops.
Hi Visuwesh,
I was down the rabbit hole on this one and now, I need some fresh air
and, hopefully, advices from experts here.
The culprit seems to be that `shell-filename-completion' does not know
how to complete the filename when the point is on '-' with the following
input in the *shell* buffer:
$ rm -pos1.xyz
And it is due to the fact that `comint-word' is only looking for a word
*backward*. I don't understand why is that so I tried to make
`comint-word' also looking for a word forward. But then the following
assertion in `completion-in-region' is violated:
(cl-assert (<= start (point)) (<= (point) end))
Does anyone could help me here?
--
Manuel Giraud
prev parent reply other threads:[~2025-01-07 15:01 UTC|newest]
Thread overview: 5+ 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
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
2025-01-07 15:01 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=87ikqqwtv7.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.