unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Gregor Zattler <grfz@gmx.de>
Cc: 66978@debbugs.gnu.org
Subject: bug#66978: 30.0.50; crashed when closing one of two frames
Date: Fri, 10 Nov 2023 20:07:38 +0800	[thread overview]
Message-ID: <87leb5stf9.fsf@yahoo.com> (raw)
In-Reply-To: <878r753m8y.fsf@no.lan> (Gregor Zattler's message of "Fri, 10 Nov 2023 12:01:49 +0100")

Gregor Zattler <grfz@gmx.de> writes:

> I did.  It evaluated to `nil'!?
>
> Then I was not able to reproduce the crash.  I now
> re-tried with my usual configuration (and also with an
> external monitor).  But no crash.
>
> The doc string of x-synchronize warns of it's
> performance penalty, but I do not experience one.
> Might it be that the return value of nil indicates it
> does not work at all in my case?

No, x-synchronize is always successful.

> I put this expression in my everyday Emacs
> configuration for now in the hope the problem will
> re-surface some time.

Thanks for sacrificing some performance for the commendable task of
debugging Emacs.





  reply	other threads:[~2023-11-10 12:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 22:26 bug#66978: 30.0.50; crashed when closing one of two frames Gregor Zattler
2023-11-07  9:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-07 12:20   ` Gregor Zattler
2023-11-07 12:24     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-07 13:48       ` Gregor Zattler
2023-11-08  0:49         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-08 16:05           ` Gregor Zattler
2023-11-08 23:52             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-10 11:01 ` Gregor Zattler
2023-11-10 12:07   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-11-21 15:28     ` Gregor Zattler

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=87leb5stf9.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=66978@debbugs.gnu.org \
    --cc=grfz@gmx.de \
    --cc=luangruo@yahoo.com \
    /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).