From: "João Távora" <joaotavora@gmail.com>
To: Psionic K <psionik@positron.solutions>
Cc: 68568@debbugs.gnu.org, Jonas Bernoulli <jonas@bernoul.li>
Subject: bug#68568: transient.el interns potentially enormous symbols as commands
Date: Sun, 21 Jan 2024 08:33:00 +0000 [thread overview]
Message-ID: <CALDnm52EFgzcmZfk4qwzu=JHcjf0EUKE49GVv_N69gG0oQqQRA@mail.gmail.com> (raw)
In-Reply-To: <CADQMGARJfC8bObeNsPyAGMcmRc=CzuME=10C77pkMyb8mB-uCw@mail.gmail.com>
Sun, Jan 21, 2024 at 8:26 AM Psionic K <psionik@positron.solutions> wrote:
> GPTel is on the user side of transient. Karthink or another contributor wrote GPTel to use transient that way. Perhaps they need to create new suffixes dynamically, but even that can be done with `define-suffix' etc. If someone calls `define-suffix' with a really long name, there's nothing transient can or should do about it.
It should probably not intern that stuff in the obarray.
UNLESS you know of a reason to. Do you?
> True, but the symbols in question contain "transient:" and ":--" strings that should be easy to filter out. Lots of completion packages can filter those.
Why should a completion package know about "transient"
or this :-- and be slowed down by this crud?
next prev parent reply other threads:[~2024-01-21 8:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 11:50 bug#68568: transient.el interns potentially enormous symbols as commands João Távora
2024-01-21 4:27 ` Psionic K
2024-01-21 7:15 ` João Távora
2024-01-21 7:29 ` Psionic K
2024-01-21 8:10 ` João Távora
2024-01-21 8:26 ` Psionic K
2024-01-21 8:33 ` João Távora [this message]
2024-01-27 9:15 ` Eli Zaretskii
2024-01-27 18:18 ` Jonas Bernoulli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-01 10:24 ` Eli Zaretskii
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='CALDnm52EFgzcmZfk4qwzu=JHcjf0EUKE49GVv_N69gG0oQqQRA@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=68568@debbugs.gnu.org \
--cc=jonas@bernoul.li \
--cc=psionik@positron.solutions \
/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).