From: Ihor Radchenko <yantar92@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, larsi@gnus.org, 57148@debbugs.gnu.org,
alain.cochard@unistra.fr, 57147@debbugs.gnu.org
Subject: bug#57147: bug#57148: 27.2; Problem with kill-new
Date: Sat, 13 Aug 2022 17:21:21 +0800 [thread overview]
Message-ID: <87zgg85wj2.fsf@localhost> (raw)
In-Reply-To: <83lersmzyn.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> But I can reproduce with Emacs 28.1 the problem I have with org-mode
>> (https://list.orgmode.org/87czd8e7wf.fsf@localhost/).
>
> The changes Po Lu mentions were done in Emacs 29, so please try that
> if you can.
I can reproduce using Emacs 29:
GNU Emacs 29.0.50
Development version e2ccd358c9d5 on master branch; build date 2022-07-17.
--
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92
next prev parent reply other threads:[~2022-08-13 9:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 23:59 bug#57148: 27.2; Problem with kill-new Alain.Cochard
2022-08-12 0:34 ` bug#57147: " Ihor Radchenko
2022-08-12 15:53 ` bug#57148: " Lars Ingebrigtsen
2022-08-13 1:59 ` bug#57147: " Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-13 2:43 ` Alain.Cochard
2022-08-13 6:15 ` bug#57148: " Eli Zaretskii
2022-08-13 9:21 ` Ihor Radchenko [this message]
2022-08-13 9:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-13 9:56 ` Ihor Radchenko
2022-08-13 11:54 ` bug#57148: " Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-13 12:20 ` Ihor Radchenko
2022-08-13 12:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-13 12:32 ` Lars Ingebrigtsen
2022-08-13 13:13 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-13 14:37 ` Ihor Radchenko
2022-08-14 1:19 ` Po Lu 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
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=87zgg85wj2.fsf@localhost \
--to=yantar92@gmail.com \
--cc=57147@debbugs.gnu.org \
--cc=57148@debbugs.gnu.org \
--cc=alain.cochard@unistra.fr \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.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).