From: Juri Linkov <juri@linkov.net>
To: Daniel Mendler <mail@daniel-mendler.de>
Cc: 48356@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
JD Smith <jdtsmith@gmail.com>
Subject: bug#48356: 28.0.50; choose-completion discards the suffix after the completion boundary
Date: Sun, 20 Mar 2022 22:34:28 +0200 [thread overview]
Message-ID: <868rt42wiz.fsf@mail.linkov.net> (raw)
In-Reply-To: <86r173odnm.fsf@mail.linkov.net> (Juri Linkov's message of "Tue, 15 Mar 2022 09:53:01 +0200")
>>>> IMHO, the root of the problem is in completion-all-completions
>>>> that returns in the last `cdr' only the start of completions,
>>>> but not the end of completions.
>>>
>>> Agreed.
>>
>> If I recall correctly, someone wrote a patch which fixed the root cause.
>
> The only patch that removes these comments
>
> ;; FIXME: We need to additionally return the info needed for the
> ;; second part of completion-base-position.
>
> ;; FIXME: We should pay attention to completion
> ;; boundaries here, but currently
> ;; completion-all-completions does not give us the
> ;; necessary information.
>
> is https://lists.gnu.org/archive/html/emacs-devel/2021-08/msg00412.html
> in bug#47711 and bug#48841.
I wonder what is the fate of this patch? There was a long discussion
without a clear outcome. Maybe it's possible to split the patch
to smaller parts where a separate patch would add the feature needed here
to return the end position of the completion boundaries?
next prev parent reply other threads:[~2022-03-20 20:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 17:23 bug#48356: 28.0.50; choose-completion discards the suffix after the completion boundary Daniel Mendler
2022-03-13 17:56 ` Juri Linkov
2022-03-13 20:35 ` bug#48356: [External] : " Drew Adams
2022-03-14 3:10 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-14 18:53 ` Juri Linkov
2022-03-14 20:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-15 2:14 ` Daniel Mendler
2022-03-15 7:53 ` Juri Linkov
2022-03-20 20:34 ` Juri Linkov [this message]
2024-04-08 21:59 ` Dmitry Gutov
2024-04-08 22:27 ` Dmitry Gutov
2024-04-08 23:50 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-10 1:33 ` Dmitry Gutov
2024-04-10 2:38 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-11 1:00 ` Dmitry Gutov
2024-04-11 6:55 ` Eli Zaretskii
2024-04-11 10:36 ` Dmitry Gutov
2024-04-11 21:59 ` Dmitry Gutov
2024-04-14 16:44 ` Juri Linkov
2024-04-14 23:55 ` Dmitry Gutov
2024-04-18 14:25 ` Spencer Baugh
2024-04-20 0:12 ` Dmitry Gutov
2024-05-04 2:23 ` Dmitry Gutov
2024-05-09 2:33 ` 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=868rt42wiz.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=48356@debbugs.gnu.org \
--cc=jdtsmith@gmail.com \
--cc=mail@daniel-mendler.de \
--cc=monnier@iro.umontreal.ca \
/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.