From: Psionic K <psionik@positron.solutions>
To: "João Távora" <joaotavora@gmail.com>
Cc: 68568@debbugs.gnu.org, Psionic K <psionik@positron.solutions>,
Jonas Bernoulli <jonas@bernoul.li>
Subject: bug#68568: transient.el interns potentially enormous symbols as commands
Date: Sun, 21 Jan 2024 17:26:35 +0900 [thread overview]
Message-ID: <CADQMGARJfC8bObeNsPyAGMcmRc=CzuME=10C77pkMyb8mB-uCw@mail.gmail.com> (raw)
In-Reply-To: <CALDnm51o2i=LitR3tmyZ5xf917i-D+pkRLLmdPESoN2isLhNuA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 789 bytes --]
> Not sure what you mean by "user"
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.
Actually, I recommend taking this to GPTel. You can ping me on their
Github @psionic-k and I'll help Karthink or others consider an alternative
approach that has sensible symbol names.
> is highly likely to appear in the extremely long tail of the enormous
symbol
True, but the symbols in question contain "transient:" and ":--" strings
that should be easy to filter out. Lots of completion packages can filter
those.
[-- Attachment #2: Type: text/html, Size: 1062 bytes --]
next prev parent reply other threads:[~2024-01-21 8:26 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 [this message]
2024-01-21 8:33 ` João Távora
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADQMGARJfC8bObeNsPyAGMcmRc=CzuME=10C77pkMyb8mB-uCw@mail.gmail.com' \
--to=psionik@positron.solutions \
--cc=68568@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--cc=jonas@bernoul.li \
/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.