unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>,  emacs-devel@gnu.org
Subject: Re: undo-auto--undoable-change infloop
Date: Wed, 10 Aug 2022 04:39:45 +0200	[thread overview]
Message-ID: <87y1vwq0su.fsf@web.de> (raw)
In-Reply-To: <jwvh72l26hh.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 09 Aug 2022 04:00:10 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> But I think you can `cancel-timer` before `timer-activate`, which will
> make sure it's not in the list any more.

That solution also came to my mind.  Wastes a lot of time, though.  The
`timer-list' is traversed 3 times: First, to find the timer to delete
it, second to test if it's already present when trying to add it (your
change), third, to sort it in at the right position (though I don't
understand why that is necessary).  The list is probably never that
large so that it would matter much.

Anyway, thanks for answering and sorry for the noise,

Michael.



  reply	other threads:[~2022-08-10  2:39 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26  3:54 undo-auto--undoable-change infloop Michael Heerdegen
2022-07-26 12:04 ` Eli Zaretskii
2022-07-27  3:52   ` Michael Heerdegen
2022-07-27  4:56     ` Michael Heerdegen
2022-07-27 11:20       ` Eli Zaretskii
2022-07-28  2:51         ` Michael Heerdegen
2022-07-28  3:10           ` Solved (was: undo-auto--undoable-change infloop) Michael Heerdegen
2022-07-28  5:49             ` Eli Zaretskii
2022-07-29  0:40               ` No, not solved " Michael Heerdegen
2022-07-29  3:44                 ` No, not solved Michael Heerdegen
2022-07-29  4:12                   ` Michael Heerdegen
2022-07-29  6:05                 ` No, not solved (was: undo-auto--undoable-change infloop) Eli Zaretskii
2022-07-27 11:20     ` undo-auto--undoable-change infloop Eli Zaretskii
2022-07-27 17:06       ` Michael Heerdegen
2022-07-27 17:34         ` Eli Zaretskii
2022-07-28  2:45           ` Michael Heerdegen
2022-07-29 14:49     ` Stefan Monnier
2022-07-30  1:14       ` Michael Heerdegen
2022-07-30  4:14         ` Michael Heerdegen
2022-07-30  5:54         ` Eli Zaretskii
2022-07-30  7:23         ` Stefan Monnier
2022-07-31  4:05           ` Michael Heerdegen
2022-08-05 14:42             ` Stefan Monnier
2022-08-06  0:26               ` Michael Heerdegen
2022-08-09  4:02               ` Michael Heerdegen
2022-08-09  8:00                 ` Stefan Monnier
2022-08-10  2:39                   ` Michael Heerdegen [this message]
2022-09-21 13:28                     ` Madhu
2022-09-21 14:17                       ` timer.el API (was: undo-auto--undoable-change infloop) Stefan Monnier
2022-10-03 20:59                         ` timer.el API Michael Heerdegen
2022-10-03 22:10                           ` Stefan Monnier
2022-10-03 22:33                             ` Michael Heerdegen
2022-10-07 20:50                       ` undo-auto--undoable-change infloop Stefan Monnier
2022-10-09  2:32                         ` Madhu
2022-10-09  4:23                           ` 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=87y1vwq0su.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).