From: Eshel Yaron <me@eshelyaron.com>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: emacs-devel@gnu.org
Subject: Re: master ff3f17ca3cd: choose-completion: Retain the suffix after completion boundary
Date: Fri, 17 May 2024 10:56:06 +0200 [thread overview]
Message-ID: <m1a5koolzt.fsf@dazzs-mbp.kpn> (raw)
In-Reply-To: <m1h6f2fcdc.fsf@dazzs-mbp.kpn> (Eshel Yaron's message of "Mon, 13 May 2024 08:35:11 +0200")
Hi Dmitry,
Eshel Yaron <me@eshelyaron.com> writes:
> Dmitry Gutov <dmitry@gutov.dev> writes:
>
>> On 12/05/2024 15:38, Eshel Yaron wrote:
>>
>>> I can't seem to find this commit, though, is that on master?
>>
>> My bad, that push didn't go through. Now on master.
>
> Thanks, everything seems to work well now.
I'm afraid there might be another regression, here's what I see:
1. emacs -Q
2. C-x C-f
3. C-a C-k to clear the minibuffer
4. Insert the path an Emacs checkout, e.g. "~/checkouts/emacs/"
5. Further insert "l/mi"
6. Hit ? to pop the completions list, which includes
"lisp/minibuffer.el" and "leim/MISC-DIC/", among others.
7. Lean on M-<down> to cycle between completion candidates.
After the last fix, I see M-<down> accumulate text after point in the
minibuffer instead of replacing the part it previously inserted. Do you
see that as well?
Thanks,
Eshel
next prev parent reply other threads:[~2024-05-17 8:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <171522198055.22327.4428936546182324178@vcs2.savannah.gnu.org>
[not found] ` <20240509023301.A25B3C1F9DE@vcs2.savannah.gnu.org>
2024-05-10 16:10 ` master ff3f17ca3cd: choose-completion: Retain the suffix after completion boundary Eshel Yaron
2024-05-12 2:59 ` Dmitry Gutov
2024-05-12 12:38 ` Eshel Yaron
2024-05-12 16:03 ` Dmitry Gutov
2024-05-13 6:35 ` Eshel Yaron
2024-05-17 8:56 ` Eshel Yaron [this message]
2024-05-17 23:28 ` Dmitry Gutov
2024-05-18 6:55 ` Eshel Yaron
2024-05-18 13:33 ` Dmitry Gutov
2024-05-18 13:51 ` Eshel Yaron
2024-05-18 14:18 ` Dmitry Gutov
2024-05-29 10:05 ` Eshel Yaron
2024-05-29 10:37 ` Dmitry Gutov
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=m1a5koolzt.fsf@dazzs-mbp.kpn \
--to=me@eshelyaron.com \
--cc=dmitry@gutov.dev \
--cc=emacs-devel@gnu.org \
/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.