all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Spencer Baugh <sbaugh@janestreet.com>,
	Andrea Corallo <acorallo@gnu.org>,
	Stefan Kangas <stefankangas@gmail.com>,
	74019@debbugs.gnu.org, juri@linkov.net
Subject: bug#74019: [PATCH] Optionally preserve selected candidate across *Completions* update
Date: Sat, 26 Oct 2024 10:59:18 -0400	[thread overview]
Message-ID: <jwvy12asyt0.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <86a5erbbwl.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 26 Oct 2024 09:45:14 +0300")

> Shouldn't we stop complicating the completion machinery at some point?

Complexity knows no bounds.

OT1H I agree that the completion infrastructure would benefit from some
cleanup and is too complex in some areas.  OTOH this specific request
doesn't affect the "completion machinery", but only the
`minibuffer-completion-help` functionality which is a fairly simple part
of the code.

> what's going on is to step with a debugger through the code -- and it
> doesn't help that some of the code is in Lisp and some in C, so Lisp
> calls into C, which calls back into Lisp, etc., thus one needs to
> interrupt the stepping, fire up a different debugger, then go back.

I luckily haven't had to step through the C code of the completion in
a long while.  But the code layout could be improved to better reflect
the architecture of the system (the separation between the "backend"
(completion tables), the "middle end" (completion styles), the standard
minibuffer UI, the in-buffer UI, the completion-list-mode).

> Stefan, WDYT?  Should we close completion to further development and
> accept only bugfixes?

🙂


        Stefan






  reply	other threads:[~2024-10-26 14:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-25 21:32 bug#74019: [PATCH] Optionally preserve selected candidate across *Completions* update Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-26  6:45 ` Eli Zaretskii
2024-10-26 14:59   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-10-28 14:08     ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-27  7:55   ` Juri Linkov
2024-10-28 13:57   ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-26 14:49 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-28 13:51   ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-28 14:21     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-28 16:01       ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-29  2:53         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-29 16:25           ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-29 18:27             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=jwvy12asyt0.fsf-monnier+emacs@gnu.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=74019@debbugs.gnu.org \
    --cc=acorallo@gnu.org \
    --cc=eliz@gnu.org \
    --cc=juri@linkov.net \
    --cc=monnier@iro.umontreal.ca \
    --cc=sbaugh@janestreet.com \
    --cc=stefankangas@gmail.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 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.