From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: m43cap@yandex.com, larsi@gnus.org, 64927@debbugs.gnu.org
Subject: bug#64927: 30.0.50; kill-ring with no X
Date: Thu, 03 Aug 2023 21:26:47 +0300 [thread overview]
Message-ID: <83tttgvv6g.fsf@gnu.org> (raw)
In-Reply-To: <jwva5v86qm8.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Thu, 03 Aug 2023 12:30:36 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: m43cap@yandex.com, 64927@debbugs.gnu.org, larsi@gnus.org
> Date: Thu, 03 Aug 2023 12:30:36 -0400
>
> I think this problem was noticed when the new feature was introduced and
> we fixed the generation of the kill-ring menu, but apparently nobody
> fixed the problem in the second part of the code which generates the
> kill-ring (I remember I mentioned at the time that we should try and
> consolidate those two code paths).
Looks like that, yes.
> > Do you see any reasonably practical way to get that back?
>
> The best we can do is to use `key-valid-p` as a best-effort test to
> decide whether we're in the presence of the new or the old format, but
> it will inevitably suffer from false positives/negatives.
Not sure I understand: if key-valid-p returns nil, what do you suggest
to do with "keys" such as those produced in the scenario of this bug
report?
next prev parent reply other threads:[~2023-08-03 18:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 9:47 bug#64927: 30.0.50; kill-ring with no X Colin Baxter
2023-07-29 11:25 ` Colin Baxter
2023-08-03 9:51 ` Eli Zaretskii
2023-08-03 15:11 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-03 16:00 ` Eli Zaretskii
2023-08-03 16:06 ` Eli Zaretskii
2023-08-03 16:30 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-03 18:26 ` Eli Zaretskii [this message]
2023-08-03 21:13 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-04 6:14 ` Colin Baxter
2023-08-04 6:38 ` Eli Zaretskii
2023-08-03 19:55 ` Colin Baxter
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=83tttgvv6g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64927@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=m43cap@yandex.com \
--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.