unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Matt Beshara <m@mfa.pw>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 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 20:38:04 +1000	[thread overview]
Message-ID: <875yw73s1b.fsf@mfa.pw> (raw)
In-Reply-To: <83o89z9k8w.fsf@gnu.org>


Eli Zaretskii <eliz@gnu.org> writes:

> Specifically, it's the 'rng-state' property on the "</p>" that 
> ends a
> paragraph.  It's a massive recursive data structure, and 
> printing it
> takes a lot of memory.  Maybe nXML could arrange for these 
> properties
> to be removed when copying to the kill-ring, but would it get in 
> the
> way if you want to paste into an XML buffer?

I haven’t had time to look at the code yet, so I’m not sure what 
information the ‘rng-state’ property contains, and whether it 
would cause any problems (to me) for it to be removed when copied. 
That said, personally, I don’t think there could be any side 
effect of removing that property from copied XML which would be 
more disruptive than savehist causing Emacs to hang completely 
when trying to save my kill ring.  Also, would nXML not be able to 
recreate any missing data it needed from the ‘rng-state’ property 
if the plain text of the XML was then pasted into an nXML buffer 
again?






  reply	other threads:[~2021-08-15 10:38 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 [this message]
2021-08-15 11:25       ` Eli Zaretskii
2021-08-15 11:44         ` Lars Ingebrigtsen
2021-08-15 11:46           ` Lars Ingebrigtsen
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=875yw73s1b.fsf@mfa.pw \
    --to=m@mfa.pw \
    --cc=50061@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).