unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sean Whitton <spwhitton@spwhitton.name>
To: Juri Linkov <juri@linkov.net>, Eshel Yaron <me@eshelyaron.com>,
	Eli Zaretskii <eliz@gnu.org>
Cc: 67661@debbugs.gnu.org, control@debbugs.gnu.org, 67001@debbugs.gnu.org
Subject: bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer
Date: Fri, 22 Dec 2023 12:00:33 +0000	[thread overview]
Message-ID: <874jgaxx9a.fsf@zephyr.silentflame.com> (raw)
In-Reply-To: <86jzp898um.fsf@mail.linkov.net> (Juri Linkov's message of "Wed,  20 Dec 2023 19:14:49 +0200")

retitle 67661 30.0.50; Completion problem introduced by commit 5416896d608
thanks

Hello,

On Wed 20 Dec 2023 at 07:14pm +02, Juri Linkov wrote:

> Thanks for the reproducible test case.  It seems there is a bug somewhere in
> pcomplete-completions-at-point.  Without icomplete:
>
> 1. emacs -q
> 2. M-x eshell
> 3. ls l<TAB>
>
> says "Complete, but not unique" that is not true.
>
> There is no such problem with shell that uses comint-completion-at-point
> instead of pcomplete-completions-at-point.

I have confirmed that 5416896d608 is the commit that introduces/reveals
the problem, for my revised test case.

-- 
Sean Whitton





  reply	other threads:[~2023-12-22 12:00 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 15:30 bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer Sean Whitton
2023-12-06 17:13 ` Juri Linkov
2023-12-06 18:14   ` Sean Whitton
2023-12-06 18:41 ` Eli Zaretskii
2023-12-07 11:42   ` Sean Whitton
2023-12-09 12:09   ` Sean Whitton
2023-12-09 13:08     ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-09 13:25       ` Eli Zaretskii
2023-12-09 14:13         ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-09 14:40           ` Eli Zaretskii
2023-12-09 15:22             ` Sean Whitton
2023-12-09 16:03             ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-09 16:07               ` Sean Whitton
2023-12-09 17:19                 ` Juri Linkov
2023-12-09 19:04                   ` Sean Whitton
2023-12-10 17:46                     ` Juri Linkov
2023-12-10 21:42                       ` Sean Whitton
2023-12-11 17:15                         ` Juri Linkov
2023-12-15 12:28                           ` Sean Whitton
2023-12-19 17:29                             ` Juri Linkov
2023-12-19 18:31                               ` Sean Whitton
2023-12-19 18:58                                 ` Juri Linkov
2023-12-20 10:34                                   ` Sean Whitton
2023-12-20 17:14                                     ` Juri Linkov
2023-12-22 12:00                                       ` Sean Whitton [this message]
2023-12-23 17:38                                         ` Juri Linkov
2023-12-29 17:47                                     ` Sean Whitton
2023-12-29 18:00                                       ` Sean Whitton
2023-12-29 19:27                                         ` Eli Zaretskii
2023-12-29 20:24                                           ` Sean Whitton
2023-12-30  6:30                                             ` Eli Zaretskii
2023-12-30 10:41                                               ` Sean Whitton
2023-12-30 17:52                                                 ` Juri Linkov
2023-12-30 19:43                                                   ` Sean Whitton
2023-12-30 17:50                                             ` Juri Linkov
2023-12-30 19:43                                               ` Sean Whitton
2023-12-31  8:29                                                 ` Juri Linkov
2024-01-10  3:12                                         ` john muhl via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-10 17:55                                           ` Sean Whitton
2024-01-17 19:18                                             ` Jim Porter
2023-12-09 16:22               ` Eli Zaretskii
2023-12-07 17:28 ` Juri Linkov
2023-12-07 22:04   ` Sean Whitton
2023-12-08  6:28     ` Eli Zaretskii
2023-12-08 10:19       ` Sean Whitton

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=874jgaxx9a.fsf@zephyr.silentflame.com \
    --to=spwhitton@spwhitton.name \
    --cc=67001@debbugs.gnu.org \
    --cc=67661@debbugs.gnu.org \
    --cc=control@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=juri@linkov.net \
    --cc=me@eshelyaron.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 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).