all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: cschol2112@googlemail.com, lekktu@gmail.com, 9873@debbugs.gnu.org
Subject: bug#9873: 24.0.90; dired - window changes size when trying to delete more than one file
Date: Thu, 27 Oct 2011 15:15:39 +0200	[thread overview]
Message-ID: <4EA9597B.60702@gmx.at> (raw)
In-Reply-To: <E1RJN7R-0002Yk-J7@fencepost.gnu.org>

 >> Its introduction modifies the behavior of splitting, resizing and
 >> deleting windows in the order described in the example in the manual.
 >
 > I understand that it affects resizing (by changing which other window
 > is resized as side effect of changing the size of the window we want
 > to resize), and deleting (by controlling which window will be given
 > the space released by the deleted one).  But what is modified in the
 > behavior of splitting?

There's yet another new variable called `window-splits'.  That variable
allows to steal space from other windows when splitting, so you can
"split" windows which are otherwise too small.  Now if `window-nest' is
non-nil, `window-splits' has no effect.

 > What I mean is that the user have no way of resizing the internal
 > windows, only the live windows, AFAIK.
 >
 > A Lisp program can resize an internal window, but doing so is
 > precisely equivalent to resizing one of the live windows on the same
 > frame (again, AFAIK).

No.  Resizing an internal window with two child windows usually resizes
_both_ child windows proportionally (usually so, because edge dragging
behaves different from other forms of resizing).

 > When you talk about resizing a live window, I understand exactly what
 > is meant.

Then you know more than me.  Resizing a live window can resize all other
windows on the same frame.  Adjusting the edge of a live window can be
different from enlarging that window.  In addition, the nest and splits
status of the window affect the outcome as well.  All I know is that
when I resize a window in a certain way, I can live with the result, or
not.  In the latter case, I try to fix the behavior.  But I gave up
understanding what happens some time ago.

 > If by "vertical combination" you mean the internal window
 > that is the parent of 2 or more live windows, I can understand that as
 > well, assuming that you are talking about a Lisp program.

A vertical combination is slightly more than a parent window.  It
encompasses number and sizes of the parent's child windows too, which
can be retrieved only by looking at these child windows.  Also, a
vertical combination can be the parent of 2 or more internal windows, or
live and internal windows.

 >> By resizing their parent window or a sibling of their parent window.  Or
 >> by resizing the containing frame.  Or by resizing the minibuffer window.
 >
 > Some of these are unavailable to users.

... but maybe hidden in operations available to the user ...

 > We were talking about a user
 > option.

... which is hard to explain, I know.

martin





  reply	other threads:[~2011-10-27 13:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-26  2:03 bug#9873: 24.0.90; dired - window changes size when trying to delete more than one file Christoph Scholtes
2011-10-26  2:16 ` Juanma Barranquero
2011-10-26  2:50   ` Christoph Scholtes
2011-10-26  2:52     ` Juanma Barranquero
2011-10-26  9:22       ` martin rudalics
2011-10-26 11:08         ` Eli Zaretskii
2011-10-26 14:22           ` martin rudalics
2011-10-26 18:30             ` Eli Zaretskii
2011-10-27  9:51               ` martin rudalics
2011-10-27 10:23                 ` Eli Zaretskii
2011-10-27 13:15                   ` martin rudalics [this message]
2011-10-27  3:39         ` Christoph Scholtes
2011-10-27  9:53           ` martin rudalics
2011-10-28  8:12             ` Juri Linkov
2011-10-28 17:16               ` martin rudalics
2011-10-31 10:11                 ` Juri Linkov
2011-10-31 10:27                   ` martin rudalics
2011-11-03 19:42                     ` Juri Linkov
2012-10-04 18:31             ` Juri Linkov
2012-10-04 18:51               ` martin rudalics
2012-10-04 19:40                 ` Juri Linkov
2012-10-05  7:03                   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EA9597B.60702@gmx.at \
    --to=rudalics@gmx.at \
    --cc=9873@debbugs.gnu.org \
    --cc=cschol2112@googlemail.com \
    --cc=eliz@gnu.org \
    --cc=lekktu@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.