unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: lee <lee@yun.yagibdah.de>
To: Juri Linkov <juri@jurta.org>
Cc: 9084@debbugs.gnu.org
Subject: bug#9084: 24.0.50; displaying man pages splits the window and formats the text for the	full width of the whole frame rather than for the width of the	window the text is displayed in, which is only 1/2 the width of	the frame
Date: Thu, 21 Jul 2011 15:12:10 +0200	[thread overview]
Message-ID: <87sjpz3hhx.fsf@yun.yagibdah.de> (raw)
In-Reply-To: <874o2hf0bt.fsf@mail.jurta.org> (Juri Linkov's message of "Wed, 20 Jul 2011 18:17:27 +0300")

Juri Linkov <juri@jurta.org> writes:

>> Ok, and how do users configure emacs to automatically split windows in
>> such a way that they aren't wider (or narrower) than the text to be
>> displayed in them while achieving the window layout they want?
>
> Do you mean an algorithm like implemented in `balance-windows' (`C-x +')
> or `shrink-window-if-larger-than-buffer' (`C-x -').  Unfortunately,
> it's only for the vertical direction, and I can't find the same for the
> horizontal direction, something like `shrink-window-if-<wider>-than-buffer'.

What I mean is

a.) ways to decide in advance what size a window should have before the
    window is created and
b.) the problem of keeping an overall window layout (i. e. within a
    frame) when multiple windows are displayed.

For example, when I use gnus[1] and look at the summary of a newsgroup
in a buffer, the summary is displayed full screen.  When I display an
article, the window is split to display the article as well as the
summary.  When I write a reply like this one, the reply is displayed
full screen[2], i. e. 230 characters wide, though `fill-column' is 72.

Now when I "M-x describe-variable fill-column", the window is split in
half, displaying the reply on the left (113 characters wide) and the
description on the right side (112 characters wide).  When I "M-x info",
the window on left is switched to show the *info* buffer instead of the
reply I'm writing --- which is not what I want because in this case, it
would make much more sense if the *info* buffer was displayed in the
window on the right.

What I would want is three windows, side by side and eventually some
vertical splits in some of the windows.  I can somehow[3] get that, but
when I have it, it won't last long because gnus or whatever else will
ignore my window layout and destroy it.

Even if I could specify for all windows that /might/ show up while I'm
using emacs what sizes they should have and where on the screen I want
them displayed in relation to other windows (if those are currently
displayed) to always achieve the overall window layout I want, that's
something I don't want to do because it's way to much work.  It probably
won't make sense, anyway --- and it's actually one of the strengths of
emacs to have dynamic window layout.

The problem would be solved if I could just "freeze" a particular window
layout or "frameify" windows.  Starting with a window the size of the
full screen, I could just split it the way I want to and then keep the
window layout as long as I want.

Having that said, it's probably not so important to have ways to specify
the possible sizes and positions of windows in advance.  It won't be
needed much if we could "frameify" windows.  What might be useful with a
static window layout would be ways to specify exceptions so that users
can decide what buffers can override their static window layout when
displayed.

That we can't "frameify" windows has probably historical reasons: The
feature doesn't make much sense when the display isn't (much) larger
than 80x25.  Nowadays, the displays are much larger.


[1] With gnus, the user can configure the window layout to some extend.
[2] I haven't bothered to find out if that is also configurable with
    gnus.  Even if it is, there's no point in changing it because
    dynamic window layout will do whatever it wants anyway.
[3] I just tried and couldn't find out how to make a window wider.  I
    would have to read the documentation, which would probably destroy
    the window configuration I'm trying to make, so I gave up to get on
    with the reply.

-- 
http://www.asciiribbon.org/
http://tools.ietf.org/html/rfc1855
http://www.caliburn.nl/topposting.html





  parent reply	other threads:[~2011-07-21 13:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-14 21:07 bug#9084: 24.0.50; displaying man pages splits the window and formats the text for the full width of the whole frame rather than for the width of the window the text is displayed in, which is only 1/2 the width of the frame lee
2011-07-15  0:46 ` Juri Linkov
2011-07-15  7:30   ` martin rudalics
2011-07-16 15:48     ` lee
2011-07-16 23:18       ` Juri Linkov
2011-07-17 13:12         ` bug#9084: 24.0.50; displaying man pages splits the window and formats the text forthe full width of the whole frame rather than for the width ofthe window the text is displayed in, which is only 1/2 thewidth " Drew Adams
2011-07-17 14:23         ` bug#9084: 24.0.50; displaying man pages splits the window and formats the text for the full width of the whole frame rather than for the width of the window the text is displayed in, which is only 1/2 the width " lee
2011-07-17 23:08           ` Juri Linkov
2011-07-18 17:56             ` lee
2011-07-19  0:34               ` Juri Linkov
2011-07-19 17:22                 ` lee
2011-07-20 15:17                   ` Juri Linkov
2011-07-20 17:36                     ` martin rudalics
2011-07-21 12:53                       ` bug#9084: 24.0.50; displaying man pages splits the window and formats the text forthe full width of the whole frame rather than for the width ofthe window the text is displayed in, which is only 1/2 thewidth " Drew Adams
2011-07-21 13:05                       ` Drew Adams
2011-07-21 14:20                       ` bug#9084: 24.0.50; displaying man pages splits the window and formats the text for the full width of the whole frame rather than for the width of the window the text is displayed in, which is only 1/2 the width " lee
2011-07-21 23:27                       ` Juri Linkov
2011-07-22  6:29                         ` martin rudalics
2011-07-25 11:18                           ` Juri Linkov
2011-07-21 13:12                     ` lee [this message]
2011-07-21 23:28                       ` Juri Linkov
2011-07-22  8:44                         ` lee
2011-07-16 23:08     ` Juri Linkov

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=87sjpz3hhx.fsf@yun.yagibdah.de \
    --to=lee@yun.yagibdah.de \
    --cc=9084@debbugs.gnu.org \
    --cc=juri@jurta.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).