From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: reza <reza@housseini.me>
Cc: 58921@debbugs.gnu.org
Subject: bug#58921: Tab completion hangs in eshell
Date: Wed, 02 Nov 2022 08:28:38 +0100 [thread overview]
Message-ID: <m2pme5x1ax.fsf@Mini.fritz.box> (raw)
In-Reply-To: <010201842d4961c3-56e13f9e-0c67-4fd2-9731-657c131da32c-000000@eu-west-1.amazonses.com> (reza@housseini.me's message of "Mon, 31 Oct 2022 09:04:54 +0000")
reza <reza@housseini.me> writes:
> Open an eshell:
>
> M-x eshell <enter>
>
> Type this command in the eshell
>
> tab --warning=no-timestamp -xf <tab>
>
> emacs will hang and has to be killed.
>
> This behavior does not occur when only typing
>
> tar -xf <tab>
Didn't check 28. On master, it gets into a loop which can be
interrupted with C-g. Backtrace is
Debugger entered--Lisp error: (quit)
pcomplete-match("\\`--suffix=" 0)
pcomplete/tar()
pcomplete-completions()
pcomplete-completions-at-point()
completion--capf-wrapper(pcomplete-completions-at-point all)
run-hook-wrapped(completion--capf-wrapper pcomplete-completions-at-point all)
completion-at-point()
funcall-interactively(completion-at-point)
call-interactively(completion-at-point nil nil)
command-execute(completion-at-point)
Maybe this helps someone knowing pcomplete.
next prev parent reply other threads:[~2022-11-02 7:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2cb2b8aa-0813-5eae-3bfc-27831b3d50dd@housseini.me>
2022-10-31 9:04 ` bug#58921: Tab completion hangs in eshell reza via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-02 7:28 ` Gerd Möllmann [this message]
2023-02-10 7:34 ` Jim Porter
2023-02-23 6:57 ` Jim Porter
2023-02-23 18:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-23 19:25 ` Jim Porter
2023-02-23 19:34 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-23 20:43 ` Jim Porter
2023-03-04 5:37 ` Jim Porter
2023-03-08 23:53 ` Jim Porter
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=m2pme5x1ax.fsf@Mini.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=58921@debbugs.gnu.org \
--cc=reza@housseini.me \
/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.