unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Yuan Fu <casouri@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: A ton of marker entry in buffer-und-list
Date: Fri, 26 Feb 2021 12:48:42 -0500	[thread overview]
Message-ID: <04692508-554F-426B-BFE6-1C4A9B7D6307@gmail.com> (raw)
In-Reply-To: <834khzq7iv.fsf@gnu.org>

>> 
>> I know what they mean but it is quite strange to have some many of (#<marker at 27 in a> . -1) in
>> buffer-undo-list—it is a new buffer and I didn’t create any marker in it, so it shouldn’t have hundreds of
>> markers to move.
> 
> hard to say without seeing the code which produces this effect.  What
> is at position 27 in buffer 'a’?

I just opened a fundamental buffer and held on ‘a’ to insert a bunch of a’s. So it’s just the character ‘a’.

Turns out it’s not my code’s fault, I bisected my configuration and disabled winner-mode, then everything is back to normal. I looked at winner.el but it doesn’t seem to create markers, only accessing marker returned by window-prev-buffers (ah, so that marker is probably the window’s point marker). So I’m not sure what went wrong.

If you start emacs -q, enable winner-mode, insert a bunch of text, and undo all of them, you should see many marker entries in buffer-undo-list. (More specifically, I inserted a line of ‘a’, copied the line and pasted a bunch of them.)

> In many cases, most markers are created implicitly as part of overlays.
> Are there overlays in the buffer?  You can check that with `overlays-in`.

Thanks, I checked and there is no overlays. (Now I think they are windows’ point markers.)

Yuan




  reply	other threads:[~2021-02-26 17:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-26  4:32 A ton of marker entry in buffer-und-list Yuan Fu
2021-02-26  7:39 ` Eli Zaretskii
2021-02-26 13:20   ` Yuan Fu
2021-02-26 13:32     ` Eli Zaretskii
2021-02-26 17:48       ` Yuan Fu [this message]
2021-02-26 21:48         ` Michael Heerdegen
2021-02-27  7:08           ` Eli Zaretskii
2021-02-28  2:38             ` Michael Heerdegen
2021-02-28  4:20               ` Yuan Fu
2021-03-01  0:21                 ` Michael Heerdegen
2021-03-01 17:54                   ` Yuan Fu
2021-03-01 18:13                     ` Stefan Monnier
2021-03-01 23:25                     ` Michael Heerdegen
2021-03-02 20:29                       ` Yuan Fu
2021-03-03  3:40                         ` Michael Heerdegen
2021-03-03  3:53                           ` Michael Heerdegen
2021-03-03 16:04                             ` Yuan Fu
2021-03-03 22:52                               ` Michael Heerdegen
2021-02-26 15:49     ` Stefan Monnier

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=04692508-554F-426B-BFE6-1C4A9B7D6307@gmail.com \
    --to=casouri@gmail.com \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@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.
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).