all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 23093@debbugs.gnu.org, nljlistbox2@gmail.com
Subject: bug#23093: 25.0.92; Change for the worse: minibuffer completion window splits below rather that right
Date: Fri, 25 Mar 2016 11:05:06 +0300	[thread overview]
Message-ID: <83shzf0yq5.fsf@gnu.org> (raw)
In-Reply-To: <56F4EBE9.4040208@gmx.at> (message from martin rudalics on Fri, 25 Mar 2016 08:42:33 +0100)

> Date: Fri, 25 Mar 2016 08:42:33 +0100
> From: martin rudalics <rudalics@gmx.at>
> CC: Eli Zaretskii <eliz@gnu.org>, 23093@debbugs.gnu.org
> 
>  > Sorry to be suggesting more work, but I think a brief entry about the
>  > new *Completions* buffer display behaviour should go in NEWS, referring
>  > the reader to your new node in the manual for details and for
>  > information on how to restore the former behaviour.
> 
> Should be done now.  Please have a look.

Thanks.  However, I have a difficulty understanding this part of the
NEWS entry:

  *** The minibuffer completions window is now displayed at the bottom of
  the selected frame and always fit to its buffer.

There are 2 unclear aspects here: (a) who is "it" in "its buffer", and
(b) what does "fit to" mean.

Does the following rewording convey the same ideas?

  *** The window displaying the '*Completions*' buffer with minibuffer
  completion candidates is now shown at the bottom of the selected
  frame.  The size of that window is always as large as required to
  display all the candidates, except when limited by the minimum size
  of the other windows on that frame; those other windows are resized
  to provide space for the '*Completions*' display.





  reply	other threads:[~2016-03-25  8:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-22 17:37 bug#23093: 25.0.92; Change for the worse: minibuffer completion window splits below rather that right N. Jackson
2016-03-22 18:47 ` martin rudalics
2016-03-22 19:02   ` Eli Zaretskii
2016-03-23  8:09     ` martin rudalics
2016-03-23 15:20       ` Eli Zaretskii
2016-03-23 18:53         ` martin rudalics
2016-03-23 19:43           ` Eli Zaretskii
2016-03-23 20:17           ` N. Jackson
2016-03-24  7:42             ` martin rudalics
2016-03-25  7:42             ` martin rudalics
2016-03-25  8:05               ` Eli Zaretskii [this message]
2016-03-25  8:37                 ` martin rudalics
2016-03-25 10:39                   ` Eli Zaretskii
2020-08-24 18:21                     ` Lars Ingebrigtsen
2016-03-22 19:45   ` N. Jackson
2016-03-23  8:09     ` martin rudalics
2016-03-23 21:35       ` Juri Linkov
2016-03-24  7:43         ` martin rudalics
2016-03-24 22:16           ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83shzf0yq5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=23093@debbugs.gnu.org \
    --cc=nljlistbox2@gmail.com \
    --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 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.