unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: martin rudalics <rudalics@gmx.at>
Cc: 46908@debbugs.gnu.org, Yuan Fu <casouri@gmail.com>
Subject: bug#46908: 28.0.50; Dozens of spurious markers in buffer-undo-list
Date: Tue, 09 Mar 2021 03:20:30 +0100	[thread overview]
Message-ID: <87czw99ifl.fsf@web.de> (raw)
In-Reply-To: <87k0qh9j6p.fsf@web.de> (Michael Heerdegen's message of "Tue, 09 Mar 2021 03:04:14 +0100")

Michael Heerdegen <michael_heerdegen@web.de> writes:

> > But how comes that `add-to-history' affects `buffer-undo-list'?
>
> `add-to-history' has no relevance here, no.  There mere existence of a
> marker in any buffer does, IIUC, cause it to be referenced by
> buffer-undo-list sooner or later, because undoing and redoing inside
> text containing a marker is not always without ambiguity regarding
> marker positioning, so the undo system adds hints to buffer-undo-list
> how these markers must be placed/repositioned.

I did some more experimentation (repeated copy, paste, undo and
garbage-collect in *scratch*), and I saw that the number of markers
living in buffer-undo-list is not monotonously increasing.  After some
time, the amount settles between 20 and 45 or so.  And stays in that
range.  Giving that a large, but still limited number of copies of the
mark marker is stored in the mark rings, that amount of markers isn't a
surprise, and if the number is not constantly growing,
everything...works as expected so far I think.  Correct?

Michael.





  reply	other threads:[~2021-03-09  2:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-03 22:45 bug#46908: 28.0.50; Dozens of spurious markers in buffer-undo-list Michael Heerdegen
2021-03-04  8:35 ` martin rudalics
2021-03-04 16:40   ` Michael Heerdegen
2021-03-04 17:20     ` martin rudalics
2021-03-04 18:35       ` Michael Heerdegen
2021-03-05  9:11         ` martin rudalics
2021-03-05  9:50           ` martin rudalics
2021-03-06  0:51             ` Michael Heerdegen
2021-03-06  7:48               ` Eli Zaretskii
2021-03-07  2:45                 ` Michael Heerdegen
2021-03-06  8:40               ` martin rudalics
2021-03-07  2:40                 ` Michael Heerdegen
2021-03-08  4:00               ` Michael Heerdegen
2021-03-08  8:26                 ` martin rudalics
2021-03-09  2:04                   ` Michael Heerdegen
2021-03-09  2:20                     ` Michael Heerdegen [this message]
2022-06-20  0:04                       ` Lars Ingebrigtsen
2022-06-20 13:56                         ` Michael Heerdegen
2021-03-09  8:10                     ` martin rudalics
2021-03-10  2:17                       ` Michael Heerdegen
2021-03-10  5:49                     ` Richard Stallman
2021-03-09  6:19                 ` Richard Stallman
2021-03-10  2:22                   ` Michael Heerdegen

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=87czw99ifl.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=46908@debbugs.gnu.org \
    --cc=casouri@gmail.com \
    --cc=rudalics@gmx.at \
    /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).