From: Dmitry Gutov <dgutov@yandex.ru>
To: meedstrom@teknik.io, 50675@debbugs.gnu.org
Subject: bug#50675: more info
Date: Sun, 5 Jun 2022 01:31:50 +0300 [thread overview]
Message-ID: <0bd70ae6-a257-92c6-dbc2-6f29de8580e4@yandex.ru> (raw)
In-Reply-To: <eeade7e29ff47b9d519ef8bbd6c8650ed328b1f9@teknik.io>
Hi!
On 08.05.2022 11:26, meedstrom--- via Bug reports for GNU Emacs, the
Swiss army knife of text editors wrote:
> Okay, so the warning message "pcomplete-completions-at-point fails to
> return valid completion data" originates from completion-at-point in
> minibuffer.el.
>
> There's a comment in there that says if the CAPF returned t, it assumes
> completion already happened. It does seem that the CAPF returns t, at
> least in eshell in a string. So that may be the root of the problem.
>
> I'm not 100% sure I'm interpreting the debugger right. To do what I did,
>
> 1. emacs -Q
> 2. M-x debug-on-entry RET pcomplete-completions-at-point RET
> 3. type a quote mark in eshell and press TAB
Sorry for the late reply.
This bug seems like a duplicate of bug#50470, which we almost got fixed,
but... then bug#55204 came around, patch merged, and the behavior
doesn't seem to reproduce anymore.
Check the latest master sometime, see if you can still trigger the problem.
next prev parent reply other threads:[~2022-06-04 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-19 14:18 bug#50675: pcomplete capf fails inside strings meedstrom--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-08 8:26 ` bug#50675: more info meedstrom--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-04 22:31 ` Dmitry Gutov [this message]
2022-08-26 12:17 ` bug#50675: pcomplete capf fails inside strings Lars Ingebrigtsen
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=0bd70ae6-a257-92c6-dbc2-6f29de8580e4@yandex.ru \
--to=dgutov@yandex.ru \
--cc=50675@debbugs.gnu.org \
--cc=meedstrom@teknik.io \
/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).