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: Wed, 3 Mar 2021 11:04:24 -0500	[thread overview]
Message-ID: <2947587D-7AFE-4580-8708-FB92B913A083@gmail.com> (raw)
In-Reply-To: <87r1kwzydl.fsf@web.de>



> On Mar 2, 2021, at 10:53 PM, Michael Heerdegen <michael_heerdegen@web.de> wrote:
> 
> Michael Heerdegen <michael_heerdegen@web.de> writes:
> 
>> Yes, I usually rebuild daily, and tried with emacs -Q.
> 
> Ok...wait.  I tried multiple times.  I "succeeded" in getting higher
> values now - 40, 60, such.  Can it be that you need to have multiple
> windows in the selected frames for this to happen?  Not winner-mode,
> just not only one window.  Or longer pauses between insertions?  Or
> using the minibuffer?  Or just repeat several times?  I'm not sure, I
> don't see a clear pattern, I get 1 marker and repeat several times and
> then suddenly 40.  Do you have a recipe that always reproduces the
> problem?

Yes, I used your function. I can’t say always, but I’ve tried 3 times and got more than one markers every time. And the reproduce recipe is very simple, I just emacs -q, see a one-window frame, hit q to go to scratch buffer, insert a’s and evaluate your function. For the insertion part, I did C-5 C-0 a, RET, C-SPC, C-p, C-SPC, C-n, M-w, C-y, C-y, C-y, … Nothing special, I think.

So I’m confused now, seems that I can reliably reproduce it but not so much on your machine, hmmm...

Yuan


  reply	other threads:[~2021-03-03 16:04 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
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 [this message]
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=2947587D-7AFE-4580-8708-FB92B913A083@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).