unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Yuan Fu <casouri@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: A ton of marker entry in buffer-und-list
Date: Mon, 1 Mar 2021 12:54:35 -0500	[thread overview]
Message-ID: <8B9B7C97-A763-47EB-98BD-7A89B03E7182@gmail.com> (raw)
In-Reply-To: <87lfb7iv04.fsf@web.de>



> On Feb 28, 2021, at 7:21 PM, Michael Heerdegen <michael_heerdegen@web.de> wrote:
> 
> Yuan Fu <casouri@gmail.com> writes:
> 
>> Hmmm, I just tried again and alas, I get the markers even without
>> winner-mode. For some reason disabling winner-mode solved it when I
>> last tested it. How strange.
> 
> Ok.
> 
> Now I used this:
> 
> #+begin_src emacs-lisp
> (defun count-markers-in-buffer-undo-list ()
>  "Message number of (different) markers in `buffer-undo-list'."
>  (interactive)
>  (require 'cl-lib)
>  (message "%d" (length
>                 (cl-delete-duplicates
>                  (seq-filter #'markerp (flatten-tree (copy-tree buffer-undo-list)))
>                  :test #'eq))))
> #+end_src
> 
> to get the number of different markers in `buffer-undo-list', after
> reproducing the recipe.  The answer was always "1".  Just a bunch of
> entries referring to one and the same marker.  That seems sane.
> 
> Are you able to provide a more pathological recipe?
> 

Using the same recipe, I got 18, the number of marker entries in each undo step. Also, even if the answer is 1, it is not ok because that shortens the number of undo a buffer can record by a factor of n (e.g., 18 in my case).

Yuan


  reply	other threads:[~2021-03-01 17:54 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
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 [this message]
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=8B9B7C97-A763-47EB-98BD-7A89B03E7182@gmail.com \
    --to=casouri@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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).