From: Richard Stallman <rms@gnu.org>
Subject: [rudalics@gmx.at: enlarge-window with preserve-before non-nil]
Date: Wed, 04 May 2005 12:25:54 -0400 [thread overview]
Message-ID: <E1DTMh8-0001LJ-14@fencepost.gnu.org> (raw)
Can someone please investigate this, and ack?
------- Start of forwarded message -------
X-Authenticated: #14592706
Date: Sun, 01 May 2005 14:21:26 +0200
From: martin rudalics <rudalics@gmx.at>
X-Accept-Language: de-DE, de, en-us, en
To: emacs-pretest-bug <emacs-pretest-bug@gnu.org>
X-Y-GMX-Trusted: 0
Subject: enlarge-window with preserve-before non-nil
Sender: emacs-pretest-bug-bounces+rms=gnu.org@gnu.org
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on monty-python
X-Spam-Level:
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63
Suppose I start with a single window called W1 (window names are
fictional)
W1
split W1 horizontally
W1 | W2
split W2 vertically
| W2
W1 |---
| W3
delete W1
W2
- --
W3
split W2 horizontally
W2 | W4
- -------
W3
split W4 vertically
| W4
W2 |---
| W5
- -------
W3
and delete W2
W4
- --
W5
- --
W3
At this moment I can't enlarge W5 any more by "dragging its modeline
down" - the window configuration appears "frozen". The attempt to
shrink W5 by dragging its modeline "up" has an effect similar to that of
dragging W4's modeline down, that means, W4 gets enlarged and not W3.
Likely, in this scenario siblings got confused before issuing the call
to `enlarge-window' with PRESERVE-BEFORE non-nil.
_______________________________________________
Emacs-pretest-bug mailing list
Emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
------- End of forwarded message -------
next reply other threads:[~2005-05-04 16:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 16:25 Richard Stallman [this message]
2005-05-08 20:24 ` [rudalics@gmx.at: enlarge-window with preserve-before non-nil] Jan D.
2005-05-09 21:03 ` Richard Stallman
2005-05-14 18:48 ` Jan D.
2005-05-15 15:59 ` Richard Stallman
2005-05-17 4:47 ` Jan D.
2005-05-17 11:58 ` Stefan Monnier
2005-06-06 10:43 ` Jan D.
2005-06-06 16:37 ` Richard Stallman
2005-06-27 8:35 ` martin rudalics
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=E1DTMh8-0001LJ-14@fencepost.gnu.org \
--to=rms@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).