unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: meedstrom--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 50675@debbugs.gnu.org
Subject: bug#50675: more info
Date: Sun, 08 May 2022 08:26:30 +0000	[thread overview]
Message-ID: <eeade7e29ff47b9d519ef8bbd6c8650ed328b1f9@teknik.io> (raw)
In-Reply-To: <a215bba5d50bb98891cd0cc745edaf7f@teknik.io>

[-- Attachment #1: Type: text/plain, Size: 568 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 826 bytes --]

  reply	other threads:[~2022-05-08  8:26 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 ` meedstrom--- via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-06-04 22:31   ` bug#50675: more info Dmitry Gutov
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=eeade7e29ff47b9d519ef8bbd6c8650ed328b1f9@teknik.io \
    --to=bug-gnu-emacs@gnu.org \
    --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).