From: Eli Zaretskii <eliz@gnu.org>
To: David Fussner <dfussner@googlemail.com>
Cc: stefan@marxist.se, 44794@debbugs.gnu.org
Subject: bug#44794: 28.0.50; Frame creation broken with (tool-bar-mode -1)
Date: Sun, 22 Nov 2020 21:37:08 +0200 [thread overview]
Message-ID: <83mtz9w5cr.fsf@gnu.org> (raw)
In-Reply-To: <CADF+Rtge7xMOTVqSjq80P3PNGLKSQKfUuVPxpbot47yfaoHr4Q@mail.gmail.com> (message from David Fussner on Sun, 22 Nov 2020 18:54:04 +0000)
> From: David Fussner <dfussner@googlemail.com>
> Date: Sun, 22 Nov 2020 18:54:04 +0000
> Cc: Stefan Kangas <stefan@marxist.se>, 44794@debbugs.gnu.org
>
> Forgive my incompetence, but my idea for how to do that appears to be
> faulty -- what would be the simplest way to detect which branch the
> code takes?
By stepping with GDB through that code. (But you already found the
answer by a different method.)
prev parent reply other threads:[~2020-11-22 19:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-22 12:46 bug#44794: 28.0.50; Frame creation broken with (tool-bar-mode -1) David Fussner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-22 13:43 ` David Fussner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-22 15:20 ` Stefan Kangas
2020-11-22 15:49 ` Eli Zaretskii
2020-11-22 18:08 ` David Fussner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-22 18:39 ` Eli Zaretskii
2020-11-22 18:54 ` David Fussner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-22 19:16 ` Stefan Kangas
2020-11-22 19:23 ` David Fussner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-22 19:59 ` Eli Zaretskii
2020-11-22 20:50 ` David Fussner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-22 21:47 ` David Fussner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-13 18:17 ` David Fussner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-13 18:53 ` Eli Zaretskii
2020-12-13 21:22 ` David Fussner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-19 10:42 ` Eli Zaretskii
2020-12-19 13:07 ` martin rudalics
2020-12-19 13:22 ` Eli Zaretskii
2020-12-19 15:55 ` martin rudalics
2020-12-19 18:19 ` David Fussner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-19 18:31 ` Eli Zaretskii
2020-12-21 14:42 ` J. Scott Berg
2020-12-21 15:33 ` martin rudalics
2020-12-21 17:29 ` Eli Zaretskii
2020-11-22 19:37 ` 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=83mtz9w5cr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44794@debbugs.gnu.org \
--cc=dfussner@googlemail.com \
--cc=stefan@marxist.se \
/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).