unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Matt Beshara <m@mfa.pw>, 50061@debbugs.gnu.org
Subject: bug#50061: 28.0.50; Hang caused by savehist-save when saving kill ring with large amount of data from nxml-mode buffer
Date: Sun, 15 Aug 2021 13:46:33 +0200	[thread overview]
Message-ID: <87y293nd5y.fsf@gnus.org> (raw)
In-Reply-To: <8735rbortl.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 15 Aug 2021 13:44:38 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> So I guess the mode could add those properties to
> `yank-excluded-properties' buffer-locally and that should fix this issue?

Er, no, we want to inhibit those properties from even landing in the
kill ring?  So that doesn't help.  Do we have something in Emacs that
filters the text properties when copying to the kill ring?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-08-15 11:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-15  2:46 bug#50061: 28.0.50; Hang caused by savehist-save when saving kill ring with large amount of data from nxml-mode buffer Matt Beshara
2021-08-15  7:36 ` Eli Zaretskii
2021-08-15  8:37   ` Eli Zaretskii
2021-08-15 10:38     ` Matt Beshara
2021-08-15 11:25       ` Eli Zaretskii
2021-08-15 11:44         ` Lars Ingebrigtsen
2021-08-15 11:46           ` Lars Ingebrigtsen [this message]
2021-08-15 12:16             ` Andreas Schwab
2021-08-15 13:45               ` Lars Ingebrigtsen
2021-08-15 14:07                 ` Eli Zaretskii
2021-08-15 14:23                   ` Lars Ingebrigtsen
2021-08-15 14:31                     ` Eli Zaretskii
2021-08-16 11:17                       ` Lars Ingebrigtsen
2021-08-15 22:39                 ` Matt Beshara
2021-08-16 11:17                   ` Lars Ingebrigtsen

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=87y293nd5y.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=50061@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=m@mfa.pw \
    /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).