From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 11276@debbugs.gnu.org
Subject: bug#11276: minibuffers windows can no longer explictly be resized
Date: Fri, 20 Apr 2012 12:01:57 +0200 [thread overview]
Message-ID: <4F913415.6050307@gmx.at> (raw)
In-Reply-To: <83hawej152.fsf@gnu.org>
>> >> > (The manual also says:
>> >> >
>> >> > You can resize it permanently by using the window sizing commands in
>> >> > the frame's other window, when the minibuffer is not active.
>> >> >
>> >> > I don't know what this means. It doesn't seem to work in any version of
>> >> > Emacs that I can find.)
>> >>
>> >> The terminology "in the frame's other window" seems to indicate that
>> >> this was written in an earlier century.
>> >
>> > How would you rephrase this for this century?
>>
>> Maybe "in a window adjacent to it"?
>
> What's the difference?
>
> Is your problem with the "window", in singular, or with something
> else, like "the frame"?
>
What does a term like "the frame's other window" mean? A frame can have
a couple of "other windows". It took me some while to find out that the
other window must be a full height live window.
martin
next prev parent reply other threads:[~2012-04-20 10:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 1:04 bug#11276: minibuffers windows can no longer explictly be resized Glenn Morris
2012-04-19 6:56 ` martin rudalics
2012-04-19 7:12 ` Glenn Morris
2012-04-19 10:42 ` martin rudalics
2012-04-19 14:37 ` Eli Zaretskii
2012-04-19 15:13 ` Drew Adams
2012-04-19 17:18 ` martin rudalics
2012-04-20 7:43 ` Eli Zaretskii
2012-04-20 10:01 ` martin rudalics
2012-04-20 10:16 ` Eli Zaretskii
2012-04-21 1:01 ` Glenn Morris
2012-04-19 14:31 ` Eli Zaretskii
2012-04-19 17:23 ` martin rudalics
2012-04-20 7:47 ` Eli Zaretskii
2012-04-20 10:01 ` martin rudalics [this message]
2012-04-20 10:49 ` Eli Zaretskii
2012-04-20 12:05 ` martin rudalics
2012-04-20 14:17 ` Eli Zaretskii
2012-04-20 15:31 ` martin rudalics
2012-04-19 14:28 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F913415.6050307@gmx.at \
--to=rudalics@gmx.at \
--cc=11276@debbugs.gnu.org \
--cc=eliz@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 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.