unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ivor Durham" <ivor.durham@ivor.cc>
To: <24707@debbugs.gnu.org>
Subject: bug#24707: 25.1; Window shrinks automatically after opening at normal size
Date: Tue, 25 Oct 2016 12:43:38 -0700	[thread overview]
Message-ID: <41339.5650372424$1505293776@news.gmane.org> (raw)
In-Reply-To: <83k2d8yuts.fsf@gnu.org>

I've used the iSpring screen video capture tool to record the behavior when
I launch "emacs -Q" with the DISPLAY environment variable set as
"192.168.0.103:0.0". The video is accessible on YouTube at
https://youtu.be/M0Um2F2oWx4 or I can attach it as needed.

Stepping through the video one frame at a time in Windows Movie Maker
reveals the following sequence:

1. The window first opens on the remote laptop at the expected size with a
black background, but no Emacs logo.
2. A grey square appears in the upper-left corner of the window occupying
about 1/3 of the width & height of the window.
3. The window turns white and the Emacs menu bar appears.
4. The buffer status bar appears with one empty buffer line between the menu
bar and the status bar at the top of the window. (This is the first sign
something unusual is happening.)
5. Two more menu items appear at the end of the menu bar: Lisp-Interaction
and Help
6. The window changes size automatically.
7. The status bar moves down leaving room for 3 buffer lines above it and a
"For information about GNU Emacs ..." line below it.
8. The mode in the status bar says "Lisp-Interaction" instead of
"Fundamental".

Does this give any clue about where the problem I might look for the cause
of this problem?








  parent reply	other threads:[~2016-10-25 19:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-16  7:27 bug#24707: 25.1; Window shrinks automatically after opening at normal size Ivor Durham
2016-10-16 18:00 ` Eli Zaretskii
     [not found]   ` <012901d227dd$26d5fee0$7481fca0$@durham@ivor.cc>
2016-10-16 19:09     ` Eli Zaretskii
2016-10-16 19:34       ` Ivor Durham
2016-10-25 19:43       ` Ivor Durham [this message]
     [not found]       ` <0b8a01d22ef8$15455c80$3fd01580$@durham@ivor.cc>
2016-10-25 23:06         ` Glenn Morris
2016-10-26  8:22           ` Ivor Durham
     [not found]           ` <0c1a01d22f62$0bfce7f0$23f6b7d0$@durham@ivor.cc>
2016-10-26 12:02             ` Eli Zaretskii
2016-10-26 17:06               ` Ivor Durham
     [not found]               ` <0cbd01d22fab$429aa5b0$c7cff110$@durham@ivor.cc>
2016-10-26 18:30                 ` Eli Zaretskii
2016-10-26 19:30                   ` Ivor Durham
     [not found]                   ` <0cf201d22fbf$64b861f0$2e2925d0$@durham@ivor.cc>
2016-10-26 19:49                     ` Eli Zaretskii
2016-10-31 16:39                       ` Ivor Durham
     [not found]                       ` <01ca01d23395$65f51570$31df4050$@durham@ivor.cc>
2016-10-31 20:43                         ` 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='41339.5650372424$1505293776@news.gmane.org' \
    --to=ivor.durham@ivor.cc \
    --cc=24707@debbugs.gnu.org \
    /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).