unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: David Fussner via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Kangas <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 18:08:59 +0000	[thread overview]
Message-ID: <CADF+RtjWk5oS7AgaEYwtt7j4eAvtpKg=FRO_f-QP1Z=yemd51w@mail.gmail.com> (raw)
In-Reply-To: <838satxufx.fsf@gnu.org>

Thanks for the patch, Stefan, but I'm sorry to report that it didn't
make any difference. Since the commit is a week old, and lots of users
turn off the tool bar, and no one else has reported an issue, I guess
Eli's probably right. My WM is kwin (4.11.22), if that's any help.

Strange that the issue just turned up after that commit, though. My
.emacs hasn't changed in quite a while. Is there anything I can do to
help debug this? With some guidance from you both I can run emacs
under gdb if that might produce useful information.

David.

On Sun, 22 Nov 2020 at 15:50, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Stefan Kangas <stefan@marxist.se>
> > Date: Sun, 22 Nov 2020 07:20:09 -0800
> >
> > > I bisected it to commit 36431e1679, which modifies xterm.c. Reverting
> > > that commit and rebuilding brings back the previous behavior, and all
> > > looks correct to me.
> >
> > Thank you for bisecting and the clear recipe.  This points at a recent
> > and fairly trivial patch by me, but I unfortunately can't reproduce the
> > issue here.
> >
> > There is something subtle going on here that I don't understand.  Does
> > anyone else have an idea?
>
> I suspect the WM might have something to do with this.





  reply	other threads:[~2020-11-22 18:08 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 [this message]
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

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='CADF+RtjWk5oS7AgaEYwtt7j4eAvtpKg=FRO_f-QP1Z=yemd51w@mail.gmail.com' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=44794@debbugs.gnu.org \
    --cc=dfussner@googlemail.com \
    --cc=eliz@gnu.org \
    --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).