unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Juri Linkov <juri@jurta.org>
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: Sat, 24 Dec 2011 10:26:24 +0100	[thread overview]
Message-ID: <4EF59AC0.9070808@gmx.at> (raw)
In-Reply-To: <87ipl7c8b6.fsf@mail.jurta.org>

 >> As Juri said we should be able to customize this.  But I don't like the
 >> idea of a global variable and I don't think that using the ALIST
 >> argument for this purpose is feasible either.  It's something I planned
 >> to solve with the help of specifiers once ...
 >
 > I'm just curious do you plan to use display specifiers or window parameters?

Display specifiers make sense only if you can merge them and people
didn't like the idea of merging.  The problem is that for certain
buffers creating or reusing a small window might make sense while for
other buffers it doesn't.

Dave, for example, apparently does use small windows since otherwise
`display-buffer' couldn't reuse them.  But he doesn't want
`save-some-buffers' reuse his small windows.  So a global variable is
hardly useful here and we probably have to use the ALIST argument of
`display-buffer'.

Window parameters OTOH are currently not customizable.  We could give a
window a `display-buffer-no-reuse' (which would be equivalent to setting
the dedicatedness of that window to something non-nil-t) or
`display-buffer-no-split' parameter.  Again we needed some means to
specify this via the ALIST argument.

martin





  reply	other threads:[~2011-12-24  9:26 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
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 [this message]
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=4EF59AC0.9070808@gmx.at \
    --to=rudalics@gmx.at \
    --cc=10186@debbugs.gnu.org \
    --cc=dave@boostpro.com \
    --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).