From: Dave Abrahams <dave@boostpro.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 10186@debbugs.gnu.org
Subject: bug#10186: 23.3; save-some-buffers not making review windows large enough
Date: Fri, 02 Dec 2011 09:34:14 -0500 [thread overview]
Message-ID: <m2hb1joxeh.fsf@boostpro.com> (raw)
In-Reply-To: <4ED8D8F1.9070307@gmx.at> (martin rudalics's message of "Fri, 02 Dec 2011 14:56:01 +0100")
on Fri Dec 02 2011, martin rudalics <rudalics-AT-gmx.at> wrote:
>>> The window has the size provided by `display-buffer'. What are your
>>> values of `split-height-threshold' and `split-width-threshold'?
>>
>> nil
>
> This means that you get a two-windows frame and your window is still too
> small? In this case I would suggest popping up a frame instead.
No, my frame is huge. The problem is that it is already divided up,
including a small window that sometimes/often gets chosen by Emacs for
display-buffer.
>> and 160, respectively.
>
>>> Setting `enable-recursive-minibuffers' to a non-nil value should allow
>>> to do that.
>>
>> I've always been leery of doing that, just because I figured it's
>> disabled-by-default for a reason, but I will try it. That said, doing
>> something that's considered "unsafe for novices" shouldn't be required
>> in order to make something so basic as save-some-buffers work, should
>> it?
>
> Doesn't C-M-v work with the default `display-buffer' approach?
I don't know; I've never tried it. I don't often try to do anything to
a window other than the current one without leaving it. I'm a fairly
experienced Emacs user; it seems to me that if I was stumped by this
there must be a problem.
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
next prev parent reply other threads:[~2011-12-02 14:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 19:08 bug#10186: 23.3; save-some-buffers not making review windows large enough Dave Abrahams
2011-12-02 8:56 ` martin rudalics
2011-12-02 10:31 ` Dave Abrahams
2011-12-02 13:56 ` martin rudalics
2011-12-02 14:34 ` Dave Abrahams [this message]
2011-12-02 16:20 ` martin rudalics
2011-12-07 16:51 ` Juri Linkov
2011-12-07 17:08 ` Drew Adams
2011-12-07 19:54 ` Juri Linkov
2022-04-21 13:55 ` Lars Ingebrigtsen
2022-05-20 10:06 ` Lars Ingebrigtsen
2011-12-23 16:02 ` Dave Abrahams
2011-12-23 16:33 ` martin rudalics
2011-12-23 21:11 ` Juri Linkov
2011-12-24 9:26 ` martin rudalics
2011-12-24 18:50 ` Juri Linkov
2011-12-24 19:30 ` Dave Abrahams
2011-12-25 10:51 ` Stefan Monnier
2011-12-23 16:05 ` Dave Abrahams
2011-12-23 16:33 ` martin rudalics
2011-12-27 17:48 ` Dave Abrahams
2022-05-20 13:22 ` bug#10186: Change the default for 🐶’s sake! Dave Abrahams
2022-05-20 13:39 ` Lars Ingebrigtsen
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=m2hb1joxeh.fsf@boostpro.com \
--to=dave@boostpro.com \
--cc=10186@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).