unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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, 13 Dec 2020 20:53:23 +0200	[thread overview]
Message-ID: <83tuspczbw.fsf@gnu.org> (raw)
In-Reply-To: <CADF+RthEYZsOyu00Ap+pXAMANyfJMNmkL-MBFew8DKznsWvoSQ@mail.gmail.com> (message from David Fussner on Sun, 13 Dec 2020 18:17:41 +0000)

> From: David Fussner <dfussner@googlemail.com>
> Date: Sun, 13 Dec 2020 18:17:41 +0000
> Cc: Stefan Kangas <stefan@marxist.se>, 44794@debbugs.gnu.org
> 
> Stefan's commit did _not_ cause the bug, merely uncovered it. Kwin was
> setting a minimum frame size for frames that matched the original
> initial frame title "emacs@system_name", so when Stefan changed that
> to "GNU Emacs at system_name" kwin no longer resized the frame, and
> that seems to be the root of the problem. (I haven't any idea whatever
> where that kwin setting came from.)
> 
> Having eliminated the kwin setting, I was able to bisect again and
> found that 2c0cd9008 was the culprit

If the original problem was due to kwin, and you solved it, then what
additional problem remains after that, for which you looked for the
culprit by bisection?

> which was J. Scott Berg's fix
> for bug #44002 involving the vcxsrv X server on Windows. Reverting
> that commit fixes my issue. Stepping through the code suggests that
> his extra test in xterm.c (l. 8950) is preventing a resize event when
> creating a new frame on my machine when tool-bar-mode is off. With
> that mode on, the resize event still occurs, and new frames are
> created normally.

Then what was the problem that kwin was responsible for?





  reply	other threads:[~2020-12-13 18:53 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 [this message]
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=83tuspczbw.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).