[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Weird frame/buffer interaction

From: EXT-Broida, Michael P
Subject: RE: Weird frame/buffer interaction
Date: Thu, 7 Mar 2002 13:32:34 -0600

OK, here's info suggested/requested by the Emacs "BUGS" manual section.

This is all about that "Magic Resizing" that happens when dragging a
modebar down "beyond" the minimum size for all windows below that bar.

Following chunks of info are:
1) "M-x report-emacs-bug" output
        (Please read the embedded small note with "RecentInput"
         additions that will help see EXACTLY what I did from
         starting Emacs until beginning the "report-emacs-bug".)
2) System info
3) Emacs mods made.
4) Contents of .emacs and site-start.el files
5) How to reproduce the problem.
6) Termscript info

        Let me know if you need more info.  I'll try to stop
        guessing about the causes; I don't know the Emacs internals
        enough to make good guesses.  <grin>

To: address@hidden
Subject: Magic Resizing
--text follows this line--
This bug report will be sent to the Free Software Foundation,
not to your local site managers!
Please write in English, because the Emacs maintainers do not have
translators to read other languages for them.

Your bug report will be posted to the address@hidden mailing list,
and to the gnu.emacs.bug news group.

In GNU Emacs 21.1.1 (i386-msvc-nt4.0.1381)
 of 2001-10-22 on buffy
configured using `configure --with-msvc (12.00)'
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: ENU
  locale-coding-system: iso-latin-1
  default-enable-multibyte-characters: t

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

Test case matches "20 line frame" I sent you previously:
one 20-line frame, three 6 line windows (+1 line minibuffer)
on separate buffers each with 10 lines of numbers.  Drag
top modebar downwards to the point where all LOWER windows
reach minimum size, drag a bit further down and all the
lower windows "magically" resize.  The motion in this small
test window is "vigorous/violent" and CONTINUOUS until the
mouse is released or moved upwards.
See the "BROIDA NOTE" immediately following the Recent Input
block!! That shows ALL input from start of Emacs.

Recent input:
C-x ^ C-x ^ C-x o C-x b t e m p 3 <return> C-y <escape> 
< <help-echo> <down-mouse-1> <help-echo> <mouse-movement> 
<help-echo> <mouse-movement> <help-echo> <mouse-movement> 
<help-echo> <mouse-movement> <mouse-movement> <help-echo> 
<mouse-movement> <help-echo> <mouse-movement> <mouse-movement> 
<help-echo> <mouse-movement> <help-echo> <mouse-movement> 
<help-echo> <mouse-movement> <mouse-movement> <help-echo> 
<mouse-movement> <help-echo> <mouse-movement> <help-echo> 
<mouse-movement> <mouse-movement> <help-echo> <mouse-movement> 
<help-echo> <mouse-movement> <help-echo> <mouse-movement> 
<help-echo> <mouse-movement> <help-echo> <mouse-movement> 
<help-echo> <mouse-movement> <help-echo> <mouse-movement> 
<mouse-movement> <mouse-movement> <mouse-movement> 
<mouse-movement> <mouse-movement> <mouse-movement> 
<mouse-movement> <mouse-movement> <mouse-movement> 
<mouse-movement> <mouse-movement> <mouse-movement> 
<mouse-movement> <mouse-movement> <mouse-movement> 
<mouse-movement> <mouse-movement> <mouse-movement> 
<mouse-movement> <mouse-movement> <drag-mouse-1> M-x 
r e p o r t - e m a c s - b u g <return>

The above is the best I could get in a BugReport capture; in
most cases, the "mouse-movement" entries were so numerous that
no keystrokes remained in the list.  I did the capture once
BEFORE I started the mouse dragging in order to get ALL the
inputs up to that point.  (The above was from a repeat of the
full testing.)  If you add the following block right BEFORE
the above Recent Input block, you'll have EVERYTHING that I
did from the time I opened Emacs.
C-x b t e m p 1 <return> 1 <return> 2 <return> 3 <return> 
4 <return> 5 <return> 6 <return> 7 <return> 8 <return> 
9 <return> 1 0 <return> C-@ <escape> < <escape> w C-x 
2 C-x 2 C-x ^ C-x ^ C-x o C-x b t e m p 2 <return> 
C-y <escape> < C-x ^ 

Recent messages:
For information about the GNU Project and its goals, type C-h C-p.
Loading image...done
Mark set [6 times]
Loading emacsbug...done

        WinNT 4.0 with SP6 (I'm pretty sure about the SP#,
        but can't find that info without rebooting.).

        Emacs pre-compiled binaries with pre-compiled Lisp stuff.
                Installed "normally": extract files and run addpm.exe.
                NO mods made other than adding diff.exe and diff3.exe
                 program files to bin directory and setting up the
                 site-start.el file (below).
        Installed in "C:\emacs-21.1" directory.

        NO .emacs file present anywhere on the system.
        Contents of site-start.el file: (one line)
(setq initial-frame-alist '((top . 1) (left . 1) (width . 70) (height .
        Use that to get the frame size for the test case.
        No other init files that I know of; if any exist,
        they came with the default download/install.
        (No other users of this system at all.)

        To reproduce the problem, just do everything in
        the RecentInput list (including the added BROIDA
        NOTE at the end of that list).  All of the "mouse-
        movement" events are from grabbing the right half
        of the topmost modebar and dragging it downwards
        until it goes nuts.  <grin>
        Started Emacs by clicking on the desktop icon.

        Termscript info: "M-: (open-termscript "~/termscript")
        results in "nil" in the minibuffer.  This is just
        a vanilla DELL monitor on a dual-Pentium3 system.

Please holler if you need more info!

> ----------
> From:         Richard Stallman[SMTP:address@hidden
> Reply To:     address@hidden
> Sent:         Wednesday, March 06, 2002 8:30 PM
> To:   address@hidden
> Cc:   address@hidden; address@hidden; address@hidden
> Subject:      Re: Weird frame/buffer interaction
> I appreciate the effort that you are making to explore the envelope of
> this bug, but that is not an effective way to get to the bottom of
> things.  Information about the envelope of the bug will never lead us
> to the cause of the problem.  That is not the way problems are found.
> What would in fact help is a test case that we can really try.  I
> cannot try the test case that was sent because I can't do anything
> with such a tall frame.  Can you find a test case which uses
> an ordinary size frame?
> I suggest you read the Bugs section in the Emacs manual, which
> explains what information will actually help find the bug.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]