unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sullivan Beck <sulbeck@ufl.edu>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 4954@debbugs.gnu.org
Subject: bug#4954: 23.1; Emacs hangs when two run-at-time calls in effect
Date: Thu, 26 Aug 2021 17:30:33 -0400	[thread overview]
Message-ID: <d8fe28fa-3a13-c4b2-6442-817bd33ad2f1@ufl.edu> (raw)
In-Reply-To: <87o89kt0ir.fsf@gnus.org>

I'm sorry, but this was so long ago that you should just go ahead and 
close it.

I believe I rewrote one to not use the run-at-time function, and that 
has resolved my problem.  However, I don't know if the base problem, 
whatever that was, still exists.

On 8/26/21 4:27 PM, Lars Ingebrigtsen wrote:
> [External Email]
> 
> Sullivan Beck <sulbeck@ufl.edu> writes:
> 
>> I wrote two simple emacs extensions, both of which use the run-at-time
>> function periodically write some information to a file. When one or the
>> other is loaded, emacs works fine. When both are loaded, emacs will work
>> fine for a while, and then suddently start behaving very sluggishly.
> 
> (I'm going through old bug reports that unfortunately weren't
> resolved at the time.)
> 
> Are you still seeing this issue in recent Emacs versions?  I can't
> remember seeing any similar reports...
> 
> --
> (domestic pets only, the antidote for overdose, milk.)
>     bloggy blog: https://urldefense.proofpoint.com/v2/url?u=http-3A__lars.ingebrigtsen.no&d=DwIBAg&c=sJ6xIWYx-zLMB3EPkvcnVg&r=aygi6L4ukZ6N8SXtTZL5hQ&m=GRdDIa5JQL6X0gnW-VFyECvmBhStsbmvCNSqHSjnXjA&s=6wGuYeUR3doHCZDMbrgIR7u3ELAQ6wscadF0_6g0JWM&e=
> 






  reply	other threads:[~2021-08-26 21:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-18 15:41 bug#4954: 23.1; Emacs hangs when two run-at-time calls in effect Sullivan Beck
2009-11-18 23:36 ` Lennart Borgman
2009-11-19  1:29   ` Sullivan Beck
2009-11-19  1:33     ` Lennart Borgman
2021-08-26 20:27 ` Lars Ingebrigtsen
2021-08-26 21:30   ` Sullivan Beck [this message]
2021-08-27  2:53     ` Lars Ingebrigtsen

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=d8fe28fa-3a13-c4b2-6442-817bd33ad2f1@ufl.edu \
    --to=sulbeck@ufl.edu \
    --cc=4954@debbugs.gnu.org \
    --cc=larsi@gnus.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.
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).