unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: Avoiding 'with-temp-buffer' in tight loops
Date: Mon, 12 Aug 2024 13:55:59 +0300	[thread overview]
Message-ID: <865xs6huww.fsf@gnu.org> (raw)
In-Reply-To: <1fd87820-d8fa-4d86-97c7-99d695b401db@gmx.at> (message from martin rudalics on Mon, 12 Aug 2024 09:51:36 +0200)

> Date: Mon, 12 Aug 2024 09:51:36 +0200
> Cc: emacs-devel@gnu.org
> From: martin rudalics <rudalics@gmx.at>
> 
>  > With respect, if you reject every solution,
> 
> I did not reject any solution.  I'm using conditional breakpoints when
> debugging 'kill-buffer' all the time, in particular to trace only those
> cases where the buffer to be killed is shown in some window.
> 
> But here I'm investigating a problem where Emacs hangs and kill -TSTP
> doesn't get me anything useful.  I suspect that 'kill-buffer' might be
> involved but have no real clue yet.  So the buffer may be any buffer
> including those created by 'with-temp-buffer' and not tracing those
> buffers with the debugger would be of no help.
> 
>  > don't expect this to be
>  > solved any time soon.
> 
> Don't worry.  I fixed this locally so it won't bother me any more here.
> 
> Apologies for wasting your time.  It won't happen again.

You didn't waste my time, I was trying to help you solve your problem,
given what I understood from your descriptions.  But if no proposal
satisfies your needs, I guess there's no solution, at least not one
that you haven't tried already.



      reply	other threads:[~2024-08-12 10:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-09  8:30 Avoiding 'with-temp-buffer' in tight loops martin rudalics
2024-08-09 10:36 ` Eli Zaretskii
2024-08-10 13:59   ` martin rudalics
2024-08-10 14:11     ` Eli Zaretskii
2024-08-12  7:51       ` martin rudalics
2024-08-12 10:55         ` Eli Zaretskii [this message]

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=865xs6huww.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rudalics@gmx.at \
    /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).