From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>, "'martin rudalics'" <rudalics@gmx.at>
Cc: 'Dave Abrahams' <dave@boostpro.com>, 10186@debbugs.gnu.org
Subject: bug#10186: 23.3; save-some-buffers not making review windows large enough
Date: Wed, 7 Dec 2011 09:08:04 -0800 [thread overview]
Message-ID: <D3E0A5F2E5DD4859A44E0C690161EFAB@us.oracle.com> (raw)
In-Reply-To: <8762hse5x1.fsf@mail.jurta.org>
> I think there should a rule for display-buffer to skip small windows.
Apologies for not following this thread. But what would be the definition of a
"small window"? And what if the buffer content itself is "small"?
A priori, this doesn't sound like such a great idea. Seems like it would be
prone to DWIM blindness.
Just a caveat from ignorance. Don't let it stop you from proposing something
concrete.
next prev parent reply other threads:[~2011-12-07 17:08 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
2011-12-02 16:20 ` martin rudalics
2011-12-07 16:51 ` Juri Linkov
2011-12-07 17:08 ` Drew Adams [this message]
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=D3E0A5F2E5DD4859A44E0C690161EFAB@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=10186@debbugs.gnu.org \
--cc=dave@boostpro.com \
--cc=juri@jurta.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).