From: Lars Ingebrigtsen <larsi@gnus.org>
To: JD Smith <jdtsmith@gmail.com>
Cc: 55491@debbugs.gnu.org
Subject: bug#55491: All completion fragments get added to obarray
Date: Wed, 18 May 2022 13:03:10 +0200 [thread overview]
Message-ID: <87y1yzdrwx.fsf@gnus.org> (raw)
In-Reply-To: <F08967E1-82E3-4F56-88B6-C71106F7C03E@gmail.com> (JD Smith's message of "Tue, 17 May 2022 18:50:41 -0400")
JD Smith <jdtsmith@gmail.com> writes:
> Thanks for your thoughts. The context is fairly specific — using
> cape-super-capf to compose two CAPF’s: elisp-completion-at-point and
> cape-dabbrev. This results in incorrect test-completion calls which
> interfere with candidate selection. With your nudge, I discovered
> this is because cape is not handling the elisp--shorthand-aware-*
> predicates returned by the elisp completion system in all cases, so it
> can be fixed there.
Ah, I see.
> I guess whether this constitutes a bug depends on whether anyone would
> expect unbound completion fragments to pollute the obarray.
I think it's "always" been like this, so it may be unlikely to be
changed. But I have to admit that I have no idea why completion is
interning stuff. Does anybody know? It does seem counter intuitive.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-18 11:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 20:22 bug#55491: All completion fragments get added to obarray JD Smith
2022-05-17 20:30 ` Lars Ingebrigtsen
2022-05-17 22:50 ` JD Smith
2022-05-18 11:03 ` Lars Ingebrigtsen [this message]
2022-05-18 11:07 ` Lars Ingebrigtsen
2022-05-18 22:19 ` Richard Stallman
2022-05-20 0:03 ` Lars Ingebrigtsen
2022-06-04 17:59 ` Dmitry Gutov
2022-06-05 14:15 ` Lars Ingebrigtsen
2022-06-05 23:36 ` Dmitry Gutov
2022-06-06 12:44 ` Lars Ingebrigtsen
2022-06-06 21:30 ` Dmitry Gutov
2022-06-07 9:30 ` Lars Ingebrigtsen
2022-06-11 0:46 ` 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
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=87y1yzdrwx.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=55491@debbugs.gnu.org \
--cc=jdtsmith@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 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).